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: Karl Dubost <karld@opera.com>
Date: Wed, 16 Jan 2013 00:23:57 +0900
Message-Id: <360A0ACE-4CA6-400A-BFE9-7DFF89AAB439@opera.com>
Cc: Piotr Dobrogost <p@ietf.dobrogost.net>, ietf-http-wg@w3.org
To: Julian Reschke <julian.reschke@gmx.de>

Le 15 janv. 2013 à 21:21, Julian Reschke a écrit :
>> - If merging, merge only those fields which are known to be safe to merge ie. those, which can be parsed after merging. Also, if the top most production in BNF specyfing field's value is #(values) it does NOT mean the field is safe for merging although this seems to be implied by the statement in the spec starting with "Multiple header fields with the same field name MUST NOT be sent (...)"
> 
> If a spec uses the list production but then doesn't allow proper parsing then that spec is buggy (such as Set-Cookie).


I still have very hard time to understand how the statement "MUST NOT be sent " is working, if it seems good to in fact not enforce it. Should it be dropped?


-- 
Karl Dubost - http://dev.opera.com/
Developer Relations, Opera Software
Received on Tuesday, 15 January 2013 15:24:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 January 2013 15:24:38 GMT