184.108.40.206 Sending a Response (All Request Types)
This section specifies common steps that MUST be performed whenever the server sends a response to a request from the client.
The response sent by the server MUST NOT specify any of the headers and tokens defined in section 2.2.1 that are defined only for use in requests.
The response MUST NOT specify any of the headers and tokens specified in section 2.2.1 that are defined only for use in responses sent to clients with a version number higher than the version number specified by the Client-Version variable in the abstract data model.
The server MUST specify the Server (section 220.127.116.11) header in the response. If the higher layer specifies that the server is acting as a live encoder, the value of the server-token parameter on the Server header MUST be set to "Rex". Otherwise, it MUST be set to "Cougar". The server major and minor version number of the Server-Token MUST be set to the server major and minor version number provided by the higher layer according to the Server table (section 18.104.22.168).
The server SHOULD specify the Supported (section 22.214.171.124) header in the response. If specified, the header MUST correctly reflect the features that are supported by the server in the response if the version number specified by the Client-Version variable is greater than or equal to 9.0. If the Supported header is specified, the header MUST correctly reflect the features that are supported by the server. The server MUST support the following feature: com.microsoft.wm.sswitch (section 126.96.36.199.4). The server SHOULD support the following features: com.microsoft.wm.fastcache (section 188.8.131.52.1), com.microsoft.wm.predstrm (section 184.108.40.206.2), com.microsoft.wm.srvppair (section 220.127.116.11.3), and com.microsoft.wm.startupprofile (section 18.104.22.168.5).<70>
The server SHOULD specify the Cache-Control (section 22.214.171.124) header in the response to prevent caching proxy servers that do not understand the Windows Media HTTP Streaming Protocol from caching the response. The Cache-Control header can contain directives, as specified in section 126.96.36.199. The higher layer resolves which of these directives, if any, are included in the Cache-Control header. The server SHOULD query the higher layer for information about which directives are required to be included on the Cache-Control header.
The server SHOULD specify the Content-Type header if the response is to a GET request, unless the message body of the response will be empty.
If the higher layer indicates that a cookie is sent, then the server SHOULD specify the Set-Cookie header as specified in section 188.8.131.52.
If the Client-ID variable in the abstract data model has been assigned a value, the server MUST specify a client-id token on a Pragma header in the response. The value of the client-id token MUST be equal to the value of the Client-ID variable.
If the response includes a client-id token on the Pragma header, the Pragma header SHOULD also include the timeout (section 184.108.40.206.29) token. The value of the timeout token MUST be set to a value less than or equal to the timeout interval of the Idle-Timeout timer. It is recommended that the value of the token be at least a few seconds less than the timeout interval, to allow for processing delays and network delays.
If the Playlist-gen-id variable in the abstract data model has a nonzero value, the server MUST specify a playlist-gen-id token on a Pragma header in the response. The value of the playlist-gen-id token MUST be equal to the value of the Playlist-gen-id variable.
The Idle-Timeout timer MUST be started, unless the value of the Session-State variable in the abstract data model is STREAMING.