W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

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

From: Mark Nottingham <mnot@mnot.net>
Date: Wed, 16 Jan 2013 09:09:32 +1100
Cc: Julian Reschke <julian.reschke@gmx.de>, Piotr Dobrogost <p@ietf.dobrogost.net>, ietf-http-wg@w3.org
Message-Id: <6D9EA8FA-50A6-44B1-A2EF-BB428E94183C@mnot.net>
To: Karl Dubost <karld@opera.com>
Saying that headers can only be combined under certain circumstances doesn't mean that they're required to be combined.

Cheers,


On 16/01/2013, at 3:23 AM, Karl Dubost <karld@opera.com> wrote:

> 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?

--
Mark Nottingham   http://www.mnot.net/
Received on Tuesday, 15 January 2013 22:10:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 January 2013 22:10:03 GMT