3.2 HTTP/1.1 Server Details

  • Article

When the HTTP/1.1 request indicates that the client supports the PeerDist content encoding, then if the response contains an ETag header field, a Last-Modified header field, or both header fields, the HTTP/1.1 server MAY<5> use the PeerDist content encoding. [RFC2616] section 14.11 defines content encoding usage.

The HTTP/1.1 server MAY use the PeerDist content encoding in its response to an HTTP/1.0 request if the HTTP/1.0 request includes an Accept-Encoding header field containing PeerDist.