-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/net/http2: support http2 proxy connections #26479
Comments
I think they're different bugs. This is more of a documentation or feature request to support http2 proxies. We only support http1 proxies currently. |
Is there any plan to support http2 proxy? |
same question about plan for this feature. :) |
Currently most people implement HTTPS proxies in Go with We can start to do some tricks and hack our way into getting it working, but official support from GoLang into this direction would be a lot better for everybody. |
I was looking for a way to Achieve HTTP2 with proxy added. Details. Could you elaborate the "We can start to do some tricks and hack our way into getting it working" @g00nix |
We should be able to get a http2 proxy working by avoiding However it would be better if this was just supported by the official lib, than having to completely rewrite the proxy functionality of |
Guys, Is there any plan to support http2 proxy? Thanks |
I guess this dialer would be a good workaround for now https://github.com/mwitkow/go-http-dialer |
This is still an issue with go 1.21. What is the roadmap for this feature? Is it a tricky one to implement?
We did the same for an explicit forward proxy. |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?What did you do?
I have an HTTP/2 proxy (I tested a custom one and https://github.com/caddyserver/forwardproxy) and when trying to connect through it from a client using HTTP/2 I get an error. This does not happen if I don't use HTTP/2.
Here's my code:
If I comment out the
http2.ConfigureTransport()
call (so it will use HTTP/1.1) it works fine.What did you expect to see?
A successful connection.
What did you see instead?
On the proxy server:
On the client:
The text was updated successfully, but these errors were encountered: