* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #88 (closed design: fixed)

Opened 7 years ago

Last modified 16 months ago

205 Bodies

Reported by: mnot@pobox.com Owned by: julian.reschke@gmx.de
Priority: later Milestone: 13
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:
Origin:

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

88.diff (2.0 KB) - added by julian.reschke@gmx.de 5 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@gmx.de 4 years ago.
Patch for part 2, clarifying the 205 requirement

Change History

comment:2 Changed 7 years ago by mnot@pobox.com

  • Component set to auth
  • Milestone set to unassigned

comment:3 Changed 7 years ago by mnot@pobox.com

  • Component changed from auth to messaging

comment:4 Changed 6 years ago by mnot@pobox.com

  • Milestone changed from unassigned to 06

comment:5 Changed 6 years ago by julian.reschke@gmx.de

  • Milestone changed from 06 to unassigned

Changed 5 years ago by julian.reschke@gmx.de

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

comment:6 Changed 5 years ago by julian.reschke@gmx.de

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 5 years ago by mnot@pobox.com

  • Priority set to low

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

comment:8 Changed 5 years ago by mnot@pobox.com

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 4 years ago by julian.reschke@gmx.de

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

comment:10 Changed 4 years ago by julian.reschke@gmx.de

  • Milestone changed from unassigned to 13

Changed 4 years ago by julian.reschke@gmx.de

Patch for part 2, clarifying the 205 requirement

comment:11 Changed 4 years ago by julian.reschke@gmx.de

From [1058]:

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

comment:12 Changed 4 years ago by julian.reschke@gmx.de

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

comment:13 Changed 4 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:14 Changed 4 years ago by mnot@pobox.com

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

comment:15 Changed 16 months ago by fielding@gbiv.com

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.