3.1.4 Higher-Layer Triggered Events

  • Article

An HTTP/1.0 or an HTTP/1.1 client MAY<4> include the PeerDist content encoding in its Accept-Encoding header field value of its HTTP request that it sends, as shown in the following example.

 Accept-Encoding: gzip, deflate, peerdist

If the client chooses to use the PeerDist content encoding for an HTTP request, the client MUST also include the PeerDist parameters header field in the same HTTP request. As shown in the following example, the PeerDist parameters header field MUST contain the Version parameter containing the highest version of the PeerDist content encoding that the client supports.

 X-P2P-PeerDist: Version=1.0

If the PeerDist parameters header field contains a Version parameter equal to 1.1, then the client MUST also include a PeerDistEx parameters header field which MUST include MinContentInformation and MaxContentInformation parameters indicating the minimum and maximum version of the PeerDist Content Information structure that the client supports.

 X-P2P-PeerDistEx: MinContentInformation=1.0, MaxContentInformation=2.0