Opened 9 years ago

Closed 9 years ago

#429 closed design (wontfix)

Combining Headers

Reported by: mnot@… Owned by:
Priority: normal Milestone: unassigned
Component: p1-messaging Severity: In WG Last Call
Keywords: Cc:

Description (last modified by mnot@…)

In one reads

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

In practice, naive implementation can result in unintended results, e.g.,


Some implementations will choose the 1st one, some will choose the 2nd one, and some may see the merged, (a valid URI).

Change History (2)

comment:1 Changed 9 years ago by mnot@…

  • Description modified (diff)

comment:2 Changed 9 years ago by fielding@…

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

Conclusion on the list is that we don't need to address this further than what has already been covered for framing.

Note: See TracTickets for help on using tickets.