Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The HTTP interface is used to send and receive data from and to an HTTP server. The HTTP data point definition table defines all HTTP data points that are used within the project.

File location

<WorkspaceDirectory>\DataFiles\xio.HTTP.DatapointDefinitions.dat


Col#Parameter DescriptionScopeUnitMandatory / default value
1NameThe name of the data point. In combination with the Path, it must be unique.stringnonemandatory
2Path

The structure that is used to represent the data point. In combination with the Name, it must be unique.

stringnoneempty
3Data typeThe type of the data point. BOOL, STR, BYTE, CHAR, INT8, UINT8, INT16, UINT16, INT32, UINT32, INT64, UINT64, FLOAT, DOUBLE, DATE, TIMEnoneSTR
4Access modeThe access rights of the data point. Allowed values are R (read-only), W (write-only), RW (read and writable).R, W, RWnoneR
5Polling UrlThe URL which is used to retrieve the data point value. The server polls by HTTP GET requests to this URL. If empty, polling is not available.stringnoneempty
6Polling intervalThe polling interval in milliseconds.50 – 65535ms5000
7Polling ResourceThe resource that is used for polling. It has to match the name that is used in the HTTP resource definition.Reference to HTTP resource definitionnoneempty
8Polling ParametersA comma-separated list of parameters that are used to replace the placeholders within the polling resource ({0}, {1}, ...).stringmsempty
9Update UrlThe URL which is used to update the data point values. The server issues HTTP PUT, POST or GET requests to this URL. If empty, updating of the values is not possible.stringnoneempty
10Update MethodThe web update request method. POST, PUT, GETnonePOST
11Update ResourceThe resource that is used for updating. It has to match the name that is used in the HTTP resource definition.Reference to HTTP resource definitionnoneempty
12Update ParametersA comma-separated list of parameters that are used to replace the placeholders within the update resource ({0}, {1}, ...).stringnoneempty
13PersistentIf enabled, the last known data point value is restored after server start up.true/falsenonefalse
14Synchronize If enabled, the value is synchronized with the backup server if used.true/falsenonetrue
15Authentication User

Username for Basic or Digest HTTP authentication if required by the HTTP server. If empty, no HTTP authentication is used.

stringnoneempty
16Authentication Password

Password for Basic or Digest HTTP authentication if required by the HTTP server. If empty, no HTTP authentication is used.

stringnoneempty
17Additional HTTP Headers

A list of additional HTTP headers which is included in each HTTP request, e.g. for authentication purposes. Additional headers must have the following form: "<key1>: <value1>\r\n<key2>: <value2>\r\n<key3>: <value3>..."

stringnoneempty
18Authentication MethodThe authentication method (Basic or Digest) if required by the HTTP server.None, Basic, Digest, BearernoneNone
19Authentication ConfigIf bearer authentication is used, the bearer definition name must be specified here. It has to match the name that is used in the HTTP bearer authentication.Reference to HTTP bearer authenticationnoneempty
  • No labels