- From: Willy Tarreau <w@1wt.eu>
- Date: Fri, 10 Feb 2017 12:39:32 +0100
- To: Ashok Kumar <ashokkumarj@gmail.com>
- Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Hi, On Fri, Feb 10, 2017 at 11:56:32AM +0530, Ashok Kumar wrote: > Hi All, > > rfc7230#section-4.4 talks about the Trailer header for Chunked T-E. > > I need some clarity on expected behavior from server, > > When a User-Agent sends a POST request with Chunked body and includes a > Trailer header (say with value content-md5) in the request headers, but > doesn't include any trailers after the zero chunk in the POST body. > > Should this be an error or can this be ignored? There is no reason why it should be an error, the Trailer header field only notifies the recipient that it should be prepared to receive trailers. It is more or less comparable to the Connection header field but for trailers. However if the recipient absolutely needs this trailer, it's a different story of course. > Since none of the mandatory headers can be present, I feel that this can be > ignored, You just need the empty line to mark the end of the trailers anyway. > But on the other hand, content-md5 not getting generated could be some > middle box modifying the content and stripping off the trailer? Definitely, or simply stripping it without touching the content. But see Mark's response regarding this anyway. Willy
Received on Friday, 10 February 2017 11:40:02 UTC