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

Ticket #93 (closed editorial: fixed)

Opened 7 years ago

Last modified 2 years ago

Repeating single-value header fields

Reported by: mnot@pobox.com Owned by: fielding@gbiv.com
Priority: normal Milestone: unassigned
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/4742AD00.2060406@gmx.de

Description

Section 4.2:

Multiple message-header fields with the same field-name MAY be
present in a message if and only if the entire field-value for that
header field is defined as a comma-separated list [i.e., #(values)].

Now this seems to be kind of backwards, wouldn't it be *much* clearer if it said:

Multiple message-header fields with the same field-name MUST NOT be
present in a message unless the entire field-value for that
header field is defined as a comma-separated list [i.e., #(values)].

That being said, do we have a recommendation for recipients when that requirement is violated? I would assume that servers SHOULD return a 400 (Bad Request), but what about clients?

Change History

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

  • Owner set to fielding@gbiv.com
  • Component set to messaging

I'm calling the decision on whether or not to accept the suggested text editorial.

Roy agreed to come up with text explaining why error handling isn't often specified in HTTP, to address the latter question (which is still a design issue).

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

  • Milestone set to unassigned

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

  • Milestone changed from unassigned to 06

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

  • Milestone changed from 06 to unassigned

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

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

Error handling split off to #186.

comment:6 Changed 5 years ago by ylafon@w3.org

See changeset [651]

comment:7 Changed 5 years ago by ylafon@w3.org

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

comment:8 Changed 2 years ago by julian.reschke@gmx.de

  • Severity set to Active WG Document
  • Summary changed from Repeating single-value headers to Repeating single-value header fields
Note: See TracTickets for help on using tickets.