- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 15 Jan 2013 13:21:44 +0100
- To: Piotr Dobrogost <p@ietf.dobrogost.net>
- CC: ietf-http-wg@w3.org
On 2013-01-15 12:47, Piotr Dobrogost wrote: > To summarize, from the point of view of http client library (see > https://github.com/kennethreitz/requests/issues/741): > > - The safe approach is to not merge any header fields with the same field name. Yes. > - 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). Best regards, Julian
Received on Tuesday, 15 January 2013 12:22:12 UTC