You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The existing implementation has a hardcoded "https" scheme for
all request, since it allows http scheme in the request, it should
use the scheme in the request url.
Fixesgolang/go#17257
Change-Id: Ibd9528df0328d7630ee94a006db694645625cdc9
Reviewed-on: https://go-review.googlesource.com/29975
Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
https://github.com/golang/net/blob/f09c4662a0bd6bd8943ac7b4931e185df9471da4/http2/transport.go#L1049
Here
scheme
is hardcoded tohttps
, but for #15830 the scheme may behttp
, so the request received by h2c server has wrong scheme.When using with a http2 proxy, this leads to a wrong request,
GET http://www.example.com
becomesGET https://www.example.com
when remote proxy server received, and wrong content is fetced.The text was updated successfully, but these errors were encountered: