Re: Connection: header in HTTP/2

--------
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.

-- 
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 06:23:51 UTC