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

RE: "205" status code

From: Joris Dobbelsteen <joris.dobbelsteen@mail.com>
Date: Sun, 19 Sep 2004 17:19:04 +0200
Message-ID: <B9833546B2643B43A56C4E962E13174601570F@nehemiah.joris2k.local>
To: "Joe Orton" <joe@manyfish.co.uk>
Cc: <ietf-http-wg@w3.org>

The 205 status MUST NOT contain a entity body and this includes NO
"content-length" and "transfer-encoding" headers.

Referencing RFC2616.
It is stated in 10.2.6 "205 Reset Content" as you described.

4.4 "Message Length"
Condition 1 states:
Any response message which "MUST NOT" include a message body (...) is
always terminated by the first empty line after the header fields,
regradless of the entity-header fields present in the message.

(...) gives examples of such responses, it does NOT specify them.

The behaviour of the Apache httpd proxy code conforms to the
specificion.

- Joris

>-----Original Message-----
>From: ietf-http-wg-request@w3.org 
>[mailto:ietf-http-wg-request@w3.org] On Behalf Of Joe Orton
>Sent: zondag, 19 september 2004 10:42
>To: ietf-http-wg@w3.org
>Subject: "205" status code
>
>
>The section on the 205 status code text includes the text:
>
>    "The response MUST NOT include an entity"
>
>The Apache httpd proxy code treats 205 like 204 or 304: 
>implicitly no message body, regardless of any 
>Content-Length/Transfer-Encoding headers sent. 
>
>It wasn't entirely clear whether this was correct from 2616: 
>neither section 4.3 or 4.4 mentions 205 alongside 1xx, 204 and 
>304 as responses.
>Can anyone clarify?
>
>joe
>
>
>
Received on Sunday, 19 September 2004 15:19:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:49:35 GMT