HTTP headers | Content-Encoding

HTTP headers | Accept-Encoding

Last Updated : 29 Aug, 2024

The HTTP headers Accepts-Encoding is usually a comparison algorithm of request header. All the HTTP client used to tell the server which encoding or encodings it supports. Then the server will respond in any of the supporting encoding formats. The server selects any one of the proposals, uses it and informs the client of its choice with the Content-Encoding response header.

Syntax:

Accept-Encoding: gzip | compress | deflate | br| identity| *

Note:

Multiple algorithm are also can be applicable.

Directives:

gzip: It is a compression format using the Lempel-Ziv coding (LZ77), with a 32-bit CRC.
compress: It is a compression format using the Lempel-Ziv-Welch (LZW) algorithm.
deflate: It is a compression format using the zlib structure, with the deflate compression algorithm.
br: It is a compression format using the Brotli algorithm.
identity: This directive Indicates the identity function which is always acceptable.
*: This directive matches any content encoding which can be listed in the header or not. It is the default value.

You can check how good your

Accept-Encoding

and

Content-Encoding

is working on this

.

Example:

Accept-Encoding: gzip, deflate, br

Accept-Encoding: br;q=1.0, gzip;q=0.6, *;q=0.1

To check this Accept-Encoding in action go to

Inspect Element

->

Network

check the request header for Accept-Encoding like below, Accept-Encoding is highlighted you can see.

Supported Browsers:

The browsers compatible with

HTTP headers Accept-Encoding

are listed below:

Google Chrome
Internet Explorer
Firefox
Safari
Opera

HTTP headers | Content-Encoding

S

skyridetim

Improve

Article Tags :

Similar Reads

HTTP headers | Content-Encoding

The HTTP headers Content-encoding is used to compress the media type. It informers the server which encoding the user will supported. It sends the information to the Accept-encoding. The server selects any one of the proposals, uses it and informs the client of its choice with the Content-Encoding r

HTTP headers | Accept-CH

The HTTP Accept-CH header is a response-type header that indicates the client hints that the server can support and should include in further requests. Syntax: Accept-CH: client hints Note: The client hints can be more than one and are to be separated by commas. Directives: The HTTP Accept-CH header

HTTP headers | Accept

The HTTP Accept header is a request type header. The Accept header is used to inform the server by the client that which content type is understandable by the client expressed as MIME-types. By using the Content-negotiation the server selects a proposal of the content type and informs the client of

HTTP headers | Accept-Charset

The HTTP Accept-Charset is a request type header. This header is used to indicate what character set are acceptable for the response from the server. The accept-charset header specifies the character encodings which are accepted by the client and this header also allows a user-agent to specify the c

HTTP headers | Transfer-Encoding

The HTTP Transfer-Encoding is a response-type header that performs as the hop-by-hop header, the hop-by-hop header connection is the single transport-level connection must not be re-transmitted. This header is performing between two nodes (single transport-level connection). If there is multi-node c

HTTP headers | Accept-Patch

The Patch is used for making partial changes to an existing resource. The Accept-Patch HTTP header is a response HTTP header that specifies the patch document is supported or not and also the media type that the server is able to understand. The presence of a specific patch document format in this h

HTTP headers | Expect

The HTTP headers Expect request-header field is used to indicate specific behaviors or expectations that the server needs to fulfill in order to respond to the client. Generally, Expect: 100-continue is the only expectation defined for the header field. If the data provided in the header field meets

HTTP headers | Date

Description: HTTP headers are used to pass additional information with HTTP response or HTTP request. Date HTTP header contains the date and time at which the message was generated. It is supported by all the browsers. Syntax: Date: day-name, day month year hour:minute:second GMT Directives: day-nam

HTTP headers | ETag

ETag or Entity Tag is a response-type header that works as a validator to let client make conditional requests. It makes re-validation requests more efficient by triggering request headers which help with web cache validation that makes economical use of network bandwidth. ETag is generated as ident

HTTP headers | Connection

The HTTP Connection header is a general type header that allows the sender or client to specify options that are desired for that particular connection. Instead of opening a new connection for every single request/response, Connection helps in sending or receiving multiple HTTP requests/responses us