7 TransportProtocols ToC Previous Next

7.4 OPC UA HTTPS ToC Previous Next

7.4.4 OPC UA Binary Encoding ToC Previous Next

This TransportProtocol implements the OPC UA Services using an OPC UA Binary Encoded Messages exchanged over an HTTPS connection.

Applications which support the HTTPS Profile shall support HTTP 1.1.

The body of the HTTP Messages shall be OPC UA Binary encoded blob. The Content-type shall be “application/octet-stream”.

An example HTTP request header is:

POST /UA/SampleServer HTTP/1.1
Content-Type: application/octet-stream;
Content-Length: nnnn

An example HTTP response header is:

HTTP/1.1 200 OK
Content-Type: application/octet-stream;
Content-Length: nnnn

The Message body is the request or response structure encoded as an ExtensionObject in OPC UA Binary. The Authorization header is only used for Session-less Service calls (see 7.4.2).

If the OPC UA Binary Encoding is used for a Session-less Service the HTTP request header is:

POST /UA/SampleServer HTTP/1.1 Authorization : Bearer <base64-encoded-token-data>
Content-Type: application/opcua+uabinary;
Content-Length: nnnn

Previous Next