Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values?

[Karl Dubost <[e-mail]>]

Le 16 janv. 2013 à 00:30, Julian Reschke a écrit :
> Note: current text in editor's copy is:
> 
> "A sender MUST NOT generate multiple header fields with the same field name in a message unless either the entire field value for that header field is defined as a comma-separated list [i.e., #(values)] or the header field is a well-known exception (as noted below)." -- <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging-latest.html#rfc.section.3.2.2>


but then to my earlier message, Bjoern replied:

Le 10 janv. 2013 à 00:59, Bjoern Hoehrmann a écrit :
> The Link header appears to be defined as taking a comma-separated list,
> <http://tools.ietf.org/html/rfc5988#section-5>, so the "MUST NOT" above does not apply to the Link header.


and it seems to contradict my understanding.
My initial point was:

  GET /foo/bar HTTP/1.1
  Host: blah.example.org
  Link: </2012/07/26/csstests/csshttplink.css>;rel=stylesheet
  Link: </>;rel=next
  […]

If I understand the spec, this above is forbidden. It MUST be

  GET /foo/bar HTTP/1.1
  Host: blah.example.org
  Link: </2012/07/26/csstests/csshttplink.css>;rel=stylesheet, </>;rel=next


The special case I know is "Set-Cookie" which can't be merged. others?


-- 
Karl Dubost - http://dev.opera.com/
Developer Relations, Opera Software