Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Forwarder error on HTTP2 --> HTTP headers #43
And seems to be related to the fact that the protocol version is manually overridden to http 1.1 , https://github.com/vulcand/oxy/blob/master/forward/fwd.go#L220
Any hints on which could be the best way to solve this?
I ran into this bug using Traefik proxying in front of Nginx.
Safari goes banas and tries to get the page repeatedly a lot of times. Which the user sees as responsetimes measured in seconds. Eventually safari gives up and shows you the page.
Curl shows the error in plain text
curl -v --http2 https://mysite.com * TCP_NODELAY set * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x7fa57b806200) > GET / HTTP/1.1 > Host: mysite.com > User-Agent: curl/7.50.1 > Accept: */* > * Connection state changed (MAX_CONCURRENT_STREAMS updated)! * http2 error: Invalid HTTP header field was received: frame type: 1, stream: 1, name: [connection], value: [keep-alive] * HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1) * Connection #0 to host mysite.com left intact curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)
If I disable keep-alive in Nginx
So I guess the
I have tcpdump logs if that helps.