The HTTP TE request header indicates the transfer encodings that the client supports.
The HTTP TE header is sent by a client to inform the server concerning what transfer encodings it accepts. By default, the chunked type is always supported for HTTP/1.1 connections.
There are several directives including
trailers, and the
q (quality value) parameter.
compress directive uses the Lempel-Ziv-Welch (LZW) Compression algorithm.
deflate directive uses a zlib structure to compress data.
gzip directive uses a Lempel-Zif encoding method and maintains a 32-bit CRC.
trailers directive implies that the client supports trailer fields in a chunked transfer encoding.
Use of HTTP Trailer header
Other HTTP headers are dependent on the setting of TE. For example, the HTTP Trailer header requires that TE be set to
trailers to work correctly.
Different directives can be placed in multiple HTTP headers or instead, specified on a comma-delimited line with an optional quality value:
TE: compress, deflate;q=0.7
The HTTP TE request header is sent by the client to inform the server concerning which content-encoding types it can support.