Vous lisez la version anglaise de ce contenu car il n’existe pas encore de traduction dans cette langue. Aidez-nous à traduire cet article !
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|
TE: compress TE: deflate TE: gzip TE: trailers // Multiple directives, weighted with the quality value syntax: TE: trailers, deflate;q=0.5
- A format using the Lempel-Ziv-Welch (LZW) algorithm is accepted as a transfer coding name.
- Using the zlib structure is accepted as a transfer coding name.
- A format using the Lempel-Ziv coding (LZ77), with a 32-bit CRC is accepted as a transfer coding name.
- Indicates that the client is willing to accept trailer fields in a chunked transfer coding.
When multiple transfer codings are acceptable, the
qparameter of the quality value syntax can rank codings by preference.
|RFC 7230, section 4.3: TE||Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing|
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
|Chrome Full support Yes||Edge Full support Yes||Firefox Full support Yes||IE Full support Yes||Opera Full support Yes||Safari Full support Yes||WebView Android Full support Yes||Chrome Android Full support Yes||Firefox Android Full support Yes||Opera Android Full support Yes||Safari iOS Full support Yes||Samsung Internet Android Full support Yes|
- Full support
- Full support