does 205 allow chunked encoding?

[julian.reschke@…]

"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.

Origin: user npcode in <​http://stackoverflow.com/questions/17826572/which-http-and-webdav-status-must-not-include-message-body/17827503?noredirect=1#comment26054009_17827503>

[fielding@…]

RFC2616 said "The response MUST NOT include an entity." In our current parlance, that implies a sender MUST NOT send a payload. This is distinct from MUST NOT include a body, which indicates that the body is not sent regardless of the payload fields.

See #88 and [1058].

My guess is that I oversimplified that text in a later commit to MUST send Content-Length: 0, but I can't remember why. Sorry.

[fielding@…]

From [2353]:

Restore the ability for 205 responses to be sent with a zero-length chunked body; addresses #491 and related to #88