Re: Connection: header in HTTP/2

On Tue, Sep 09, 2014 at 06:23:25AM +0000, Poul-Henning Kamp wrote:
> --------
> In message <>, 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. I'd rather handle this header just like today : strip the
header fields referenced there, consider the special tokens if needed,
and ignore the rest.


Received on Tuesday, 9 September 2014 08:11:51 UTC