Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? from Nico Williams on 2013-01-15 (ietf-http-wg@w3.org from January to March 2013)

From: Nico Williams <nico@cryptonector.com>
Date: Tue, 15 Jan 2013 17:37:08 -0600
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
Message-ID: <CAK3OfOiS1UPqvsk5H8RWUKyw8MB=uykeMkXzZoffm6732=UjMg@mail.gmail.com>

On Tue, Jan 15, 2013 at 5:28 PM, Mark Nottingham <mnot@mnot.net> wrote:
> We're talking about HTTP/1.x here, not 2.0. We can't retroactively make implementations non-conformant.

Ah, yes.  But we could stop encouraging implementors to merge multiple
header instances.  Then we only have to say that it happens and
explain the pitfalls.

Received on Tuesday, 15 January 2013 23:37:33 UTC