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

On 2013-01-09 16:32, Piotr Dobrogost wrote:
> 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?

It is a good idea to define header fields in a way so that they can be 
parsed unambiguously.

> What's special about "If-Match" and "If-None-Match" headers?

The allow ",", but do not use quoted-string syntax.

>> So to separate values in a list production, code needs to understand the syntax of the individual values.
>
> True but is this mentioned somewhere?

Not at the moment, but maybe we should mention it.

Best regards, Julian