✳flâneur — a map of the web's best reading

Transfer-Encoding header - HTTP | MDN

developer.mozilla.org · 653 words · saved by 1 readers

The HTTP Transfer-Encoding request and response header specifies the form of encoding used to transfer messages between nodes on the network. Transfer-Encoding is a hop-by-hop header, that is applied to a message between two nodes, not to a resource itself. Each segment of a multi-node connection can use different Transfer-Encoding values. If you want to compress data over the whole connection, use the end-to-end Content-Encoding header instead. In practice this header is rarely used, and in those cases it is almost always used with chunked. That said, the specification indicates that when present in a message it indicates the compression used on the message in that hop, and/or whether the message has been chunked. For example, Transfer-Encoding: gzip, chunked indicates that the content has been compressed using the gzip coding and then chunked using the chunked coding while forming the message body. The header is optional in responses to a HEAD request as these messages have no body a

Transfer-Encoding header - HTTP | MDN Skip to main content Skip to search Transfer-Encoding header Baseline Widely available This feature is well established and works across many devices and browser versions. It’s been available across browsers since July 2015. Learn more See full compatibility The HTTP Transfer-Encoding request and response header specifies the form of encoding used to transfer messages between nodes on the network. Transfer-Encoding is a hop-by-hop header , that is applied to a message between two nodes, not to a resource itself. Each segment of a multi-node connection can

Explore this link on the map →

related reading