-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Open
Labels
FeatureRequestIssues asking for a new feature that does not need a proposal.Issues asking for a new feature that does not need a proposal.NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Description
I am interested in creating a HTTP proxy (note: not a reverse proxy) in Go. I'm only interested in implementing the CONNECT method. All other methods are irrelevant for me. https://github.com/elazarl/goproxy comes very close to what I want to do, but I'm also interested in supporting CONNECT when client is connected to proxy using HTTP/2. AFAIK, according to RFC7540, CONNECT over HTTP/2 should work by hijacking the stream and do TCP tunneling over it.
*http2responseWriter does not implement http.Hijacker. One idea, would be that it implements http.Hijacker which will give access not to the underlying TCP connection but rather the HTTP stream.
...or is there any other approach I could take without having to implement low-level HTTP/2 stuff?
palkerecsenyi, crvv, tigerwill90, becheran and SevenWhitetigerwill90
Metadata
Metadata
Assignees
Labels
FeatureRequestIssues asking for a new feature that does not need a proposal.Issues asking for a new feature that does not need a proposal.NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.