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.
| 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
compressdeflategzipWhen multiple transfer codings are acceptable, the q parameter of the quality value syntax can rank codings by preference.
| Specification | Title |
|---|---|
| RFC 7230, section 4.3: TE | Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing |
| Feature | Chrome | Edge | Firefox | Internet Explorer | Opera | Safari |
|---|---|---|---|---|---|---|
| Basic support | Yes | Yes | Yes | Yes | Yes | Yes |
| Feature | Android webview | Chrome for Android | Edge mobile | Firefox for Android | IE mobile | Opera Android | iOS Safari |
|---|---|---|---|---|---|---|---|
| Basic support | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
© 2005–2018 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