HTTP/2 does not use the Connection header field to indicate
connection-specific header fields; in this protocol, connection-specific
metadata is conveyed by other means. An endpoint MUST NOT generate an
HTTP/2 message containing connection-specific header fields; any message
containing connection-specific header fields MUST be treated as
malformed (Section 8.1.2.6).
The only exception to this is the TE header field, which MAY be
present in an HTTP/2 request; when it is, it MUST NOT contain any
value other than "trailers".
Allow 'te' to have value 'trailers'.
From the HTTP2.0 spec: [https://httpwg.github.io/specs/rfc7540.html#rfc.section.8.1.2]
HTTP/2 does not use the Connection header field to indicate connection-specific header fields; in this protocol, connection-specific metadata is conveyed by other means. An endpoint MUST NOT generate an HTTP/2 message containing connection-specific header fields; any message containing connection-specific header fields MUST be treated as malformed (Section 8.1.2.6).