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

Closed
bagder opened this Issue Aug 27, 2015 · 0 comments

Projects

None yet

1 participant

@bagder
Member
bagder commented Aug 27, 2015

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.

@bagder bagder added the HTTP/2 label Aug 27, 2015
@bagder bagder added a commit that closed this issue Sep 3, 2015
@bagder bagder 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 #401
1869164
@bagder bagder closed this in 1869164 Sep 3, 2015
@jgsogo jgsogo added a commit to jgsogo/curl that referenced this issue Oct 19, 2015
@bagder @jgsogo bagder + jgsogo 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 #401
3baf321
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment