Opened 12 years ago

Closed 10 years ago

Last modified 7 years ago

#93 closed editorial (fixed)

Repeating single-value header fields

Reported by: mnot@… Owned by: fielding@…
Priority: normal Milestone: unassigned
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:

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 (8)

comment:1 Changed 12 years ago by mnot@…

  • Component set to messaging
  • Owner set to fielding@…

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 12 years ago by mnot@…

  • Milestone set to unassigned

comment:3 Changed 11 years ago by mnot@…

  • Milestone changed from unassigned to 06

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

  • Milestone changed from 06 to unassigned

comment:5 Changed 10 years ago by mnot@…

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

Error handling split off to #186.

comment:6 Changed 10 years ago by ylafon@…

See changeset [651]

comment:7 Changed 10 years ago by ylafon@…

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

comment:8 Changed 7 years ago by julian.reschke@…

  • 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.