The HTTPTErequest header specifies the transfer encodings the user agent is willing to accept.The transfer encodings are for message compression and chunking of data during transmission.

Transfer encodings are applied at the protocol layer, so an application consuming responses receives the body as if no encoding was applied.

Syntax

TE: compressTE: deflateTE: gzipTE: trailers

Multiple directives in a comma-separated list withquality values as weights:

TE: trailers, deflate;q=0.5

Directives

compress

A format using theLempel-Ziv-Welch (LZW) algorithm is accepted as a transfer coding name.

deflate

Using thezlib structure is accepted as a transfer coding name.

gzip

A format using theLempel-Ziv coding (LZ77), with a 32-bit CRC is accepted as a transfer coding name.

trailers

Indicates that the client will not discard trailer fields in achunked transfer coding.

q

When multiple transfer codings are acceptable, theq parameter (quality values) syntax orders codings by preference.

Note thatchunked is always supported by HTTP/1.1 recipients, so you don't need to specify it using theTE header.See theTransfer-Encoding header for more details.

Examples

Using the TE header with quality values

In the following request, the client indicates a preference forgzip-encoded responses withdeflate as a second preference using aq value:

GET /resource HTTP/1.1Host: example.comTE: gzip; q=1.0, deflate; q=0.8

Specifications

Browser compatibility

See also

• Transfer-Encoding
• Content-Encoding
• Trailer
• Chunked transfer encoding