- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Tue, 09 Sep 2014 08:24:56 +0000
- To: Willy Tarreau <w@1wt.eu>
- cc: HTTP Working Group <ietf-http-wg@w3.org>
-------- In message <20140909081126.GA4299@1wt.eu>, Willy Tarreau writes: >On Tue, Sep 09, 2014 at 06:23:25AM +0000, Poul-Henning Kamp wrote: >> -------- >> In message <20140909055008.GB3403@1wt.eu>, Willy Tarreau writes: >> >> >> Managing TCP connections is out-of-band in HTTP/2.0, so sending >> >> "Connection: close" or "Connection: keepalive" inside a HTTP/2.0 >> >> multiplex doesn't make any sense, should not happen and I think >> >> we should make that an explicit SHALL NOT. >> >> >> >> The general way to do that would be to make it a stream-error in >> >> HTTP/2.0 if Connection: tries to make a non-existent header hop-by-hop. >> > >> >I don't think this extra check would provide any value, to be honnest. >> >> It would catch cases where people have messed up. > >Yes, but it's contrary to the principle of being liberal about what >you accept. Can we at least implement the "be conservative" part and tell people that "Connection: close" will not work ? -- 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 Tuesday, 9 September 2014 08:25:28 UTC