Opened 12 years ago

Closed 8 years ago

Last modified 6 years ago

#88 closed design (fixed)

205 Bodies

Reported by: mnot@… Owned by: julian.reschke@…
Priority: later Milestone: 13
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:

Description

RFC2616 Section 4.3 "Message Body" enumerates those messages that don't include a message-body;

All 1xx (informational), 204 (no content), and 304 (not modified) responses MUST NOT include a message-body. All other responses do include a message-body, although it MAY be of zero length.

However, it does not list 205 (section 10.2.6).

Also if you look at the texts for 204, 304 and 205 responses, you see that 204 and 304 say "MUST NOT include a message-body", whereas 205 says "MUST NOT include an entity". 204 and 304 go on to say that the message is terminated at the first empty line, but 205 does not say that.

Attachments (2)

88.diff (2.0 KB) - added by julian.reschke@… 10 years ago.
proposed change for part 1, clarifying that 1xx, 204, 304 are all the exceptions to parsing
i88.diff (878 bytes) - added by julian.reschke@… 9 years ago.
Patch for part 2, clarifying the 205 requirement

Download all attachments as: .zip

Change History (17)

comment:2 Changed 12 years ago by mnot@…

  • Component set to auth
  • Milestone set to unassigned

comment:3 Changed 12 years ago by mnot@…

  • Component changed from auth to messaging

comment:4 Changed 11 years ago by mnot@…

  • Milestone changed from unassigned to 06

comment:5 Changed 11 years ago by julian.reschke@…

  • Milestone changed from 06 to unassigned

Changed 10 years ago by julian.reschke@…

proposed change for part 1, clarifying that 1xx, 204, 304 are all the exceptions to parsing

comment:6 Changed 10 years ago by julian.reschke@…

From [600]:

Take out language that implied that there may be methods for which a request body MUST NOT be included (related to #88)

comment:7 Changed 10 years ago by mnot@…

  • Priority set to low

Setting priority to low; Roy wants to do parsing clean-up and terminology revision before addressing this.

comment:8 Changed 10 years ago by mnot@…

proposal: remove requirement altogether (i.e., 205 response bodies don't have any defined semantic, but like the rest of HTTP, there has to be a body there, even if it is 0 length)

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

  • Owner set to julian.reschke@…
  • Severity set to Active WG Document

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

  • Milestone changed from unassigned to 13

Changed 9 years ago by julian.reschke@…

Patch for part 2, clarifying the 205 requirement

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

From [1058]:

Clarify 205's constraints for the message body (see #88)

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

  • Resolution set to incorporated
  • Status changed from new to closed

comment:13 Changed 8 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:14 Changed 8 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed

comment:15 Changed 6 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

Note: See TracTickets for help on using tickets.