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: Nico Williams <nico@cryptonector.com>
Date: Tue, 15 Jan 2013 18:07:48 -0600
Message-ID: <CAK3OfOg17M3LTPwFJXFuHrq4AZh505hq27xoeVwJsPTvA7_3aw@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Karl Dubost <karld@opera.com>, Julian Reschke <julian.reschke@gmx.de>, Piotr Dobrogost <p@ietf.dobrogost.net>, ietf-http-wg@w3.org
On Tue, Jan 15, 2013 at 6:01 PM, Mark Nottingham <mnot@mnot.net> wrote:
> On 16/01/2013, at 10:57 AM, Nico Williams <nico@cryptonector.com> wrote:
>> No.  I'm saying that it's OK for apps to do that but not any other
>> entities (middleboxes), mostly because middleboxes can't possibly know
>> about headers that hadn't been registered when they were implemented.
>
> OK. Is this an actual problem you've encountered?
>
> I'm fine with adding some clarifying text if it helps implementers, but I haven't seen this confusing any middlebox vendors; they tend to leave the bits alone...

I noticed Poul's and someone else's replies that in their middlebox
implementations they concluded that it's never safe to merge headers.
If that's the case (and I do think it follows from the facts that it
is the case) then we should say so rather than leave each implementor
to figure this out on their own.

Nico
--
Received on Wednesday, 16 January 2013 00:08:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 16 January 2013 00:08:15 GMT