W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2013

Re: draft-ietf-httpbis-p2-semantics-23, "6.3.6 205 Reset Content"

From: Roy T. Fielding <fielding@gbiv.com>
Date: Thu, 25 Jul 2013 10:39:08 -0700
Message-Id: <631B907D-D301-4E70-A9C7-6550F9A07F1F@gbiv.com>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
To: Julian Reschke <julian.reschke@gmx.de>
Yes, that was the intent. More specifically, generating chunked when there is no need to do so was considered far less interoperable than simply requiring C-L. We were able to make this a requirement because 205 was defined by the WG before any deployment.

....Roy


On Jul 24, 2013, at 11:29 PM, Julian Reschke <julian.reschke@gmx.de> wrote:

> <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-23.html#status.205>:
> 
> "Since the 205 status code implies that no additional content will be provided in the payload, the server MUST send a message body of zero length. In other words, the server MUST send a "Content-Length: 0" field in a 205 response or close the connection immediately after sending the blank line terminating the header section."
> 
> So would using Chunked Encoding be illegal? I don't think that was the intent.
> 
> The simplest possible fix seems to drop the second sentence.
> 
> Best regards, Julian
> 
> Origin: user npcode in <http://stackoverflow.com/questions/17826572/which-http-and-webdav-status-must-not-include-message-body/17827503?noredirect=1#comment26054009_17827503>
> 
Received on Thursday, 25 July 2013 17:39:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:14 UTC