Content-Encoding entity header is used to compress the media-type. When present, its value indicates which encodings were applied to the entity-body. It lets the client know how to decode in order to obtain the media-type referenced by the
The recommendation is to compress data as much as possible and therefore to use this field, but some types of resources, such as jpeg images, are already compressed. Sometimes, using additional compression doesn't reduce payload size and can even make the payload longer.
Content-Encoding: gzip Content-Encoding: compress Content-Encoding: deflate Content-Encoding: identity Content-Encoding: br // Multiple, in the order in which they were applied Content-Encoding: gzip, identity Content-Encoding: deflate, gzip
x-gzipas an alias, for compatibility purposes.
On the client side, you can advertise a list of compression schemes that will be sent along in an HTTP request. The
Accept-Encoding header is used for negotiating content encoding.
Accept-Encoding: gzip, deflate
The server responds with the scheme used, indicated by the
Content-Encoding response header.
Note that the server is not obligated to use any compression method. Compression highly depends on server settings and used server modules.
|RFC 7231, section 220.127.116.11: Content-Encoding||Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content|
|RFC 7932: Brotli Compressed Data Format||Brotli Compressed Data Format|
|Android webview||Chrome for Android||Edge Mobile||Firefox for Android||Opera for Android||iOS Safari||Samsung Internet|
© 2005–2018 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.