Skip to content
Pricing RU Sign In
RU
← All HTTP Headers
Response

Transfer-Encoding

Specifies the encoding used to transfer the response body, typically chunked.

Syntax

Transfer-Encoding: chunked | compress | deflate | gzip

Example

Transfer-Encoding: chunked

Description

Transfer-Encoding specifies how the payload is encoded for transfer. Most common value: chunked.

Chunked encoding sends data in parts, useful for dynamically generated content where total length is unknown.

Not used in HTTP/2 — the protocol has its own framing mechanism.

Check if your website sends this header correctly

Check your headers →

Related Headers

Connection
Controls whether the network connection stays open after the current transaction finishes.
Content-Disposition
Indicates whether the response should be displayed inline or downloaded as a file attachment.
Content-Encoding
Specifies the compression algorithm applied to the response body, such as gzip or brotli.
Content-Length
Specifies the size of the response body in bytes.
Content-Type
Indicates the media type of the response body, telling the browser how to interpret and display the content.
Date
Indicates the date and time at which the response was generated by the server.

Related guides

Longer-form reading on this topic from the knowledge base.

Automate this check

Set up continuous monitoring and get an alert when something breaks. No manual runs to remember.

Start free

Related Articles

HTTP

Server-Sent Events vs WebSockets: Choosing Real-Time Communication

9 min · Read → HTTP

HTTP 404 Not Found Error: 7 Causes and How to Fix

8 min · Read → HTTP

The Complete HTTP Request Lifecycle: From URL to Rendered Page

10 min · Read →
All articles →

Start monitoring for free

Sign up and get access to API, monitoring and notifications

Create Account API Documentation