Our volunteers haven't translated this article into Türkçe yet. Join us and help get the job done!
You can also read the article in English (US).

The Trailer response header allows the sender to include additional fields at the end of chunked messages in order to supply metadata that might be dynamically generated while the message body is sent, such as a message integrity check, digital signature, or post-processing status.

The TE request header needs to be set to "trailers" to allow trailer fields.

Header type Response header
Forbidden header name yes


Trailer: header-names


HTTP header fields which will be present in the trailer part of chunked messages. These header fields are disallowed:


Chunked transfer encoding using a trailing header

In this example, the Expires header is used at the end of the chunked message and serves as a trailing header.

HTTP/1.1 200 OK 
Content-Type: text/plain 
Transfer-Encoding: chunked
Trailer: Expires

Expires: Wed, 21 Oct 2015 07:28:00 GMT\r\n


Specification Title
RFC 7230, section 4.4: Trailer Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
RFC 7230, section 4.1.2: Chunked trailer part Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing

Browser compatibility

Update compatibility data on GitHub
ChromeEdgeFirefoxInternet ExplorerOperaSafariAndroid webviewChrome for AndroidEdge MobileFirefox for AndroidOpera for AndroidSafari on iOSSamsung Internet
TrailerChrome Full support YesEdge Full support YesFirefox Full support YesIE Full support YesOpera Full support YesSafari Full support YesWebView Android Full support YesChrome Android Full support YesEdge Mobile Full support YesFirefox Android Full support YesOpera Android Full support YesSafari iOS Full support YesSamsung Internet Android Full support Yes


Full support  
Full support

See also

Document Tags and Contributors

Contributors to this page: mdnwebdocs-bot, fscholz, Jeremie
Last updated by: mdnwebdocs-bot,