HTTP Binding Configuration
|URL||An expression indicating what web address to reference on the binding. If entering a static URL, quotation marks must be used.|
Any HTTP method. Used to send HTTP requests to the specified URL. Options as follows:
Used to pass key/value pairs in the header of our HTTP requests.
|Body||An expression indicating what to send in the body of our HTTP requests.|
Indicates what HTTP authentication type to use. Equivalent to specifying the Authorization key in the header. Options are None, Basic, Bearer, or Digest.
The Authentication Value field takes an expression that should indicate what authorization string or token should be used in combination with the associated authentication type. For example, if the header should contain the string:
Then the Authentication Type should be Basic and the Authentication Value should be aWduaXRpb246cGFzc3dvcmQ=.
|Connect Timeout||Indicates how long the Ignition Gateway should wait for a response to our connect request.|
|Socket Timeout||Indicates how long the Ignition Gateway should wait for a response to a given HTTP request.|
|Enabled||Indicates whether the binding should be active.|
|Overlay Opt-Out||Indicates whether the component should reflect a bad quality binding via a Tag overlay.|
Indicates whether to allow the remote web server to store cookies.
|Cache & Share|
When this setting is enabled, the binding will utilize a polling engine that is shared across all running Perspective sessions. The polling engine will poll once, cache the value, and deliver the results to all registered consumers. The cache persists for a period of time that matches the configured poll rate. This optimization is helpful for consolidating multiple identical polling tasks, particularly when you have many Perspective sessions running at once. Disabling this option will bypass the cache.
|Polling||Controls how frequently HTTP requests should be issued, and therefore how often the binding should be updated.|