- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sat, 16 May 2020 05:39:32 +0200
- To: Poul-Henning Kamp <phk@phk.freebsd.dk>, mnot@mnot.net, phk@varnish-cache.org
- Cc: Willy Tarreau <w@1wt.eu>, last-call@ietf.org, httpbis-chairs@ietf.org, ietf-http-wg@w3.org, barryleiba@gmail.com, draft-ietf-httpbis-header-structure@ietf.org
On 15.05.2020 18:06, Poul-Henning Kamp wrote: > -------- > In message <4859a11f-5649-b633-f43b-facf036e61c7@gmx.de>, Julian Reschke writes > : > >> Related to this: it just occurred to me that: >> >> Test: Foo >> Test: >> Test: Bar >> >> yields different results for fields using HTTP's list notation, and >> structured header fields. >> >> In the former case, the combined value is equivalent to >> >> Test: Foo, Bar >> >> while in the latter case, the field is malformed. >> >> I *really* think it would be better if structured header fields would >> actually be "proper" applications of the standard HTTP list ABNF. > > Considering how rarely used multiple-headers are (apart from The > Cookie Mistake) I think it would be much simpler, better and wiser > to restrict SH to single, non-concatenated headers. I have no idea what the exact proposal would be. Fail when multiple instances are there? > ... Best regards, Julian
Received on Saturday, 16 May 2020 03:40:20 UTC