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

From: Piotr Dobrogost <p@ietf.dobrogost.net>
Date: Wed, 9 Jan 2013 16:32:06 +0100
To: ietf-http-wg@w3.org
Message-ID: <CAA6tFMvPoYW+RF3qsNTRFZoFv9yUXXM8+-OFF2LkPNqCXR00vg@mail.gmail.com>

On Wed, Jan 9, 2013 at 12:00 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
>
> It's a good idea to do, but not always the case. Example: "If-Match" and
> "If-None-Match". So to separate values in a list production, code needs to
> understand the syntax of the individual values.

I don't quite understand what you meant to say above.
What is a good idea?
What's special about "If-Match" and "If-None-Match" headers?

> So to separate values in a list production, code needs to understand the syntax of the individual values.

True but is this mentioned somewhere?

Regards,
Piotr Dobrogost

Received on Wednesday, 9 January 2013 15:33:03 UTC