Share via

3.4.4.3 Sending Application Data

  • Article

To send, the KeepAlive ConnectionState MUST be in the 'Established' state, and the GetSessionReady state MUST be TRUE, and the ServerOKtoSend state MUST be TRUE. If any of the conditions are not met, the application data MUST be buffered in the order it was received.

If the application data needs to be buffered, the processing stops here.

To send, the server sends the SSTP stream data over the GET session framed within a KeepAlive-GET-Responses. The SSTP stream data is contained within the KeepAlive-GET-Response-Entity-Body. The server MUST construct a KeepAlive-Content-Length header that is equal to the length of the entity body. This content length MUST NOT exceed the 32768 octet limit imposed by the KeepAlive protocol.

The Response-Status-Line MUST be set to a status code of 200 and Reason-Phrase of "OK"

as specified in section 2.2.2.3.1.

The server constructs a KeepAlive-GET-Response as defined in section 2.2.3.3.

The Connection header with Keep-Alive token MUST be specified as specified in section 2.2.1.3 for persistent connection interoperability with HTTP 1.1 proxies as recommended in [RFC2068].

The server MUST set ServerOKtoSend to FALSE.

The server MUST send the KeepAlive-GET-Response message on the GET session.