Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The binary message content of HTTP with binary is constructed the same way as TCP with binary as shown in the Two-Way Method Invocation Using TCP-Binary section. However, the message frame is made of HTTP headers as specified in the Sending Request subsection under the HTTP Transport section.
The HTTP headers for a One-Way Method with Binary payload is shown as follows.
-
POST /MyServer.soap HTTP/1.1 User-Agent: Mozilla/4.0+(compatible; MSIE 6.0; Windows 6.0.6000.0; MS .NET Remoting; MS .NET CLR 2.0.50727.1318 ) Content-Type: application/octet-stream Host: localhost:8080 Content-Length: 607 Expect: 100-continue Connection: Keep-Alive
The HTTP request header "Content-Type" contains "application/octet-stream" indicating that the payload is binary. For HTTP there is no field in the request headers to indicate that the request is One-Way.
The server returns an HTTP response with a Status-Code of 202, as follows.
-
Version=1.1, Status-Code=202, Reason-Phrase=Accepted. Content-Length: 0 Server: MS .NET Remoting, MS .NET CLR 2.0.50727.1318