Export (0) Print
Expand All

2.1 Transport

The Manifest Request and Fragment Request messages MUST be represented as HTTP request messages, as specified by the Request rule of [RFC2616], subject to the following constraints:

  • The method MUST be "GET".

  • For the Manifest Request message, the RequestURI MUST adhere to the syntax of the ManifestRequest field, specified in section 2.2.1.

  • For the Fragment Request message, the RequestURI MUST adhere to the syntax of the FragmentRequest field, specified in section 2.2.3.

  • The HTTP-Version SHOULD be HTTP/1.1.

The Manifest Response and Fragment Response messages MUST be represented as HTTP response messages, as specified by the Response rule of [RFC2616], subject to the following constraints:

  • The Status-Code SHOULD be 200.

  • For the Manifest Response message, the message body MUST adhere to the syntax of the ManifestResponse field, specified in section 2.2.2.

  • For the Fragment Response message, the message body MUST adhere to the syntax to the FragmentResponse field, specified in section 2.2.4.

  • The HTTP-Version SHOULD be HTTP/1.1.

The Live Ingest Request MUST be represented as an HTTP request message, as specified by the Request rule of [RFC2616], subject to the following constraints:

  • The Method MUST be "POST".

  • The "Transfer-Encoding: Chunked" header SHOULD replace the "Content-Length" header.

  • The RequestURI MUST adhere to the syntax of the LiveIngestRequest field, specified in section 2.2.7.

  • The HTTP-Version SHOULD be HTTP/1.1.

Show:
© 2016 Microsoft