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

Ticket #28 (closed editorial: fixed)

Opened 7 years ago

Last modified 5 years ago

Connection closing

Reported by: mnot@pobox.com Owned by: julian.reschke@gmx.de
Priority: normal Milestone: 11
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/20050226112415.GA11563@manyfish.co.uk

Description

The phrase "unless the message is terminated by closing the connection" in Section 4.4 is unnecessary.

Section 3.6 uses the same phrase; it is a little confusing. In 4.4 you could almost read it to mean that presence of "Connection: close" would mean that a T-E header should be ignored, which is presumably not the intent (and certainly not the practice).

Attachments

i28.diff (6.6 KB) - added by julian.reschke@gmx.de 7 years ago.
Proposed patch.
i28.2.diff (6.6 KB) - added by julian.reschke@gmx.de 7 years ago.
Proposed patch.

Change History

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

  • version set to d00
  • Component set to messaging
  • Milestone set to unassigned

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

Revised proposal:

p1 4.4, "Message Length":

  1. If the Transfer-Encoding header field (section 14.41) is present and contains the "chunked" value, the transfer-length is defined by the use of the "chunked" transfer encoding.

p1 3.4, "Transfer Codings":

Whenever a transfer-coding is applied to a message-body, the set of transfer-codings MUST include "chunked", unless the message indicates it is terminated by closing the connection.

comment:3 Changed 7 years ago by julian.reschke@gmx.de

  • Owner set to julian.reschke@gmx.de

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

Proposed patch.

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

Proposed patch.

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

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

Fixed in [276]:

Resolve #28: clarify connection closing vs chunked encoding (closes #28).

comment:5 Changed 7 years ago by fielding@gbiv.com

  • Status changed from closed to reopened
  • Resolution fixed deleted

I don't think the committed text clarifies the issue.

Message length should be defined entirely by the message parsing algorithm (currently in 4.4, but destined to move up). The odd text in 3.4 should be in the parsing algorithm, not hidden away in the transfer-coding definitions.

Reopening so that we can look at it again after the message parsing text is reorganized.

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

  • Priority set to normal
  • Type changed from design to editorial

comment:7 Changed 5 years ago by fielding@gbiv.com

From [852]:

Changed message-body ABNF to be *OCTET. Specifying the actual number of octets will have to be done in prose.

Moved mistitled "Message Length" section into the Message Body section, since it only explains how many octets are in the body. Deleted useless "Entity Length" section and transfer-length term.

Addresses #28: Connection closing

Removed redundant mention of terminating by connection close and rewrote explanation so that it doesn't self-contradict.

Addresses #90: Delimiting messages with multipart/byteranges

Removed message-delimiting paragraphs of multipart/byteranges from p1 and p3.

Addresses #95: Handling multiple Content-Length headers

Added requirements for what to do if multiple or invalid Content-Length is received.

Rephrased requirements for Transfer-Encoding to only apply when a transfer-coding is present. Clarify that Transfer-Encoding overrides Content-Length and treat receiving both as an error. Clarify that only the chunked transfer-coding can delimit a message (the original design allowed other self-descriptive encodings, but that was abandoned in 2616).

Addresses #109: Clarify entity / representation / variant terminology

Entity-body terminology changed to payload in order to clarify that it is what gets packaged (as a message-body) into a message, allowing us to (eventually) distinguish between messages containing whole representations and messages containing only partial representations. Reduce use of the same terms for other things (e.g., in explanation of dates).

comment:8 Changed 5 years ago by fielding@gbiv.com

From [872]:

Addresses #28: Connection closing

Finished clarification of when closing the connection is required for message delimiting.

comment:9 Changed 5 years ago by fielding@gbiv.com

  • Status changed from reopened to closed
  • Resolution set to incorporated
  • Severity set to Active WG Document
  • Milestone changed from unassigned to 11

Incorporated as part of rewriting the message body length section and clarifying the requirements on chunked.

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

From [876]:

note work done in [872] (see #28)

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

  • Status changed from closed to reopened
  • Resolution incorporated deleted

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

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