- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Wed, 02 Jul 2014 10:22:37 +0000
- To: Julian Reschke <julian.reschke@gmx.de>
- cc: Mark Nottingham <mnot@mnot.net>, "Eric J. Bowman" <eric@bisonsystems.net>, HTTP Working Group <ietf-http-wg@w3.org>
In message <53B3DB11.9010606@gmx.de>, Julian Reschke writes: >On 2014-07-02 11:58, Mark Nottingham wrote: >> Personally - very strong +1. This is fundamental. Yes, it sucks, but it’s how HTTP works, and we can’t change it here. >> ... > >The reason why I raised this is that in HTTP/1.1, the HTTP status isn't >a header field, so the issue doesn't come up. In HTTP/2, it's a pseudo >header field, so it *could* appear in trailers, and thus people might be >tempted to take advantage of it. I think the best way to handle this textually, is to explain that :header are not really headers, but a sleigh of hand HTTP/2 uses to transmit the non-header protocol fields, and that this does not change the semantics of those fields in any way. -- 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 Wednesday, 2 July 2014 10:22:59 UTC