Opened 9 years ago

Closed 9 years ago

#491 closed design (fixed)

does 205 allow chunked encoding?

Reported by: julian.reschke@… Owned by: draft-ietf-httpbis-p2-semantics@…
Priority: normal Milestone: 24
Component: p2-semantics Severity: In WG Last Call
Keywords: Cc:


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

Change History (6)

comment:1 Changed 9 years ago by julian.reschke@…

  • Type changed from editorial to design

comment:2 Changed 9 years ago by 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.

comment:3 Changed 9 years ago by fielding@…

From [2353]:

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

comment:4 Changed 9 years ago by fielding@…

  • Milestone changed from unassigned to 24
  • Resolution set to incorporated
  • Status changed from new to closed

comment:5 Changed 9 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:6 Changed 9 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.