- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Sun, 10 Jul 2016 09:09:39 +0000
- To: Julian Reschke <julian.reschke@greenbytes.de>
- cc: Phil Hunt <phil.hunt@oracle.com>, HTTP Working Group <ietf-http-wg@w3.org>
-------- In message <683f5f58-6046-d9fb-cc75-d0ab3890ce23@greenbytes.de>, Julian Reschke writes: >On 2016-07-10 10:04, Poul-Henning Kamp wrote: >> ... >>> FWIW, duplicate headers aren't really needed, when the header field was >>> defined properly (so the only problem is Set-Cookie, see >>> <https://greenbytes.de/tech/webdav/rfc7230.html#field.order>). >> >> I'll second the call for a blanket ban on repeat headers if they >> use the new (JSON-)syntax. >> ... > >But that's not what I said. No, that is what Phil asked for: > It would be nice if the JSON encoding handled arrays so that the demand for > duplicate headers is removed. Signing could then be more successful and could > even stipulate that the presence of a repeat header in a signed request is a > failure condition. I would go as far to make all repeat header a failure condition under the new format. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Received on Sunday, 10 July 2016 09:10:08 UTC