Export (0) Print
Expand All

6 Appendix A: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs.

 

  • Windows Vista operating system

  • Windows Server 2008 operating system

  • Windows 7 operating system

  • Windows Server 2008 R2 operating system

  • Windows 8 operating system

  • Windows Server 2012 operating system

  • Windows 8.1 operating system

  • Windows Server 2012 R2 operating system

  • Windows 10 operating system

  • Windows Server 2016 operating system 

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.

<1> Section 1.6: For Windows Vista and Windows Server 2008, support for the client-side elements of this protocol is available only via the optional installation of the Background Intelligent Transfer Service (see [MC-BUP]) via Windows Management Framework. Support for the server-side elements of this protocol is not available for Windows Vista or Windows Server 2008.

<2> Section 1.7: HTTP/1.1 clients in Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 set the PeerDist version parameter to 1.0. HTTP/1.1 clients in Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2, Windows 10, and Windows Server 2016 set the PeerDist version parameter to 1.1.

<3> Section 1.7: HTTP/1.1 servers in Windows Server 2008 R2 set the PeerDist version parameter to 1.0. HTTP/1.1 servers in Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 set the PeerDist version parameter to 1.1 when responding to a client that specified a PeerDist version parameter equal to 1.1 and set the PeerDist version parameter to 1.0 when replying to a client that specified a PeerDist version parameter equal to 1.0.

<4> Section 3.1.4: HTTP/1.1 clients in Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2 operating system, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2, Windows 10, and Windows Server 2016 use the PeerDist content encoding for GET requests only.

<5> Section 3.1.4: HTTP/1.0 clients in Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016 use the PeerDist content encoding for GET requests only.

<6> Section 3.2: In Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016, the HTTP/1.1 server sends a PeerDist-encoded response.

<7> Section 3.2.5.1: The HTTP/1.1 server in Windows Server 2008 R2 uses the algorithms and data structures defined in [MS-PCCRC] to generate the PeerDist Content Information only when it receives an HTTP/1.1 request. The server runs the algorithms asynchronously, and therefore it does not use the PeerDist encoding for the response to the request that triggered the execution of the algorithms. Similarly, the server does not use the PeerDist encoding for any HTTP/1.1 requests for the same content that are received during the execution of the algorithms on that content. However, after the algorithms have completed and the PeerDist Content Information has been generated for that content, the server will respond to requests for the same content with the PeerDist Content Information for that content.

<8> Section 3.2.5.1: The HTTP/1.1 server in Windows Server 2008 R2 sends the "Connection" header field with a value of "close" if the HTTP request is a range retrieval request, and the total length of the full entity-body is greater than 1 megabyte.

<9> Section 3.2.5.1: The HTTP/1.1 server in Windows Server 2008 R2 does not send the "Connection" header field with a value of "close" if the HTTP/1.1 client is "Microsoft BITS".

Show:
© 2016 Microsoft