Skip custom Connection: headers when doing HTTP/2 #401

bagder · 2015-08-27T08:32:24Z

An application may opt to use custom Connection: headers with libcurl, but if the server supports HTTP/2 those headers are not allowed.

RFC 7540 section 8.1.2.2 states: "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"

So, to let applications keep working with HTTP/1.1 or HTTP/2, libcurl must filter out the Connection: headers for h2.


        http2: don't pass on Connection: headers

RFC 7540 section 8.1.2.2 states: "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" Closes curl#401

bagder added the HTTP/2 label Aug 27, 2015

bagder closed this in 1869164 Sep 3, 2015

lock bot locked as resolved and limited conversation to collaborators May 7, 2018

curl / curl

Skip custom Connection: headers when doing HTTP/2 #401

Skip custom Connection: headers when doing HTTP/2 #401

bagder commented Aug 27, 2015

curl / curl

Sponsor curl/curl

Join GitHub today

Skip custom Connection: headers when doing HTTP/2 #401

Skip custom Connection: headers when doing HTTP/2 #401

Comments

bagder commented Aug 27, 2015