W3cubDocs

/HTTP

TE

The TE request header specifies the transfer encodings the user agent is willing to accept. (you could informally call it Accept-Transfer-Encoding, which would be more intuitive).

See also the Transfer-Encoding response header for more details on transfer encodings. Note that chunked is always acceptable for HTTP/1.1 recipients and you that don't have to specify "chunked" using the TE header. However, it is useful for setting if the client is accepting trailer fields in a chunked transfer coding using the "trailers" value.

Syntax

TE: compress
TE: deflate
TE: gzip
TE: trailers

// Multiple directives, weighted with the quality value syntax:
TE: trailers, deflate;q=0.5

Directives

compress
A format using the Lempel-Ziv-Welch (LZW) algorithm is accepted as a transfer coding name.
deflate
Using the zlib structure is accepted as a transfer coding name.
gzip
A format using the Lempel-Ziv coding (LZ77), with a 32-bit CRC is accepted as a transfer coding name.
trailers
Indicates that the client is willing to accept trailer fields in a chunked transfer coding.
q

When multiple transfer codings are acceptable, the q parameter of the quality value syntax can rank codings by preference.

Specifications

Specification Title
RFC 7230, section 4.3: TE Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing

Browser compatibility

Feature Chrome Firefox Edge Internet Explorer Opera Safari
Basic Support (Yes) (Yes) (Yes) (Yes) (Yes) (Yes)
Feature Android Chrome for Android Edge mobile Firefox for Android IE mobile Opera Android iOS Safari
Basic Support (Yes) (Yes) (Yes) (Yes) (Yes) (Yes) (Yes)

See also

© 2005–2017 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/TE