Tutorial by Examples

The HTTP message body can be compressed (since HTTP/1.1). Either by the server compresses the request and adds a Content-Encoding header, or by a proxy does and adds a Transfer-Encoding header. A client may send an Accept-Encoding request header to indicate which encodings it accepts. The most com...

It is possible to compress an HTTP response message body more than once. The encoding names should then be separated by a comma in the order in which they were applied. For example, if a message has been compressed via deflate and then gzip, the header should look like: Content-Encoding: deflate, g...

The client first sends a request with an Accept-Encoding header that indicates it supports gzip: GET / HTTP/1.1\r\n Host: www.google.com\r\n Accept-Encoding: gzip, deflate\r\n \r\n The server may then send a response with a compressed response body and a Content-Encoding header that specifies...