Re: Connection-specific fields in HTTP/2

On Tue, Aug 24, 2021, at 16:24, Willy Tarreau wrote:
> Be careful here, "TE" is both listed as forbidden (must be treated as
> malformed) and "must not contain any value other than trailers". As
> such I'd remove it from the explicit list, as it's already implied by
> the general wording.

Good catch.  Removing it from the list means that the exception (in the next paragraph) can still apply.
 
> It's not explicitly mentioned that Connection is forbidden, it's only
> said "not used", 

Yeah, that makes sense.  I've listed that explicitly (but separately).

Received on Tuesday, 24 August 2021 07:36:35 UTC