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 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.
| Header type | Request header |
|---|---|
| Forbidden header name | yes |
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
qparameter of the quality value syntax can rank codings by preference.
Specifications
| Specification |
|---|
| Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing # header.te |
Browser compatibility
BCD tables only load in the browser