Skip to content
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

documentation: net/http/httputil: add example for reuse of Director #31393

Closed
wants to merge 1 commit into from

Conversation

syndbg
Copy link

@syndbg syndbg commented Apr 10, 2019

Ref: #31406

Updates documentation with example for reuse of Director

@googlebot googlebot added the cla: yes Used by googlebot to label PRs as having a valid CLA. The text of this label should not change. label Apr 10, 2019
@gopherbot
Copy link

This PR (HEAD: f42207e) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/go/+/171577 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link

Message from Gobot Gobot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
Within the next week or so, a maintainer will review your change and provide
feedback. See https://golang.org/doc/contribute.html#review for more info and
tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11, it means that this CL will be reviewed as part of the next development
cycle. See https://golang.org/s/release for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/171577.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link

Message from Anton Antonov:

Patch Set 1:

A bit more rationale:

Since go1.12 enhanced further the ReverseProxy implementation a closed source library (and many more open-source ones) that provide a reverse proxy for HTTP and WS can be deprecated.

The only difference between the closed source library was that I had a more convenient hook to modify a request that allowed me to focus only on the VHOST logic.

The change here would noticeably reduce the boilerplate and make developers avoid re-implementing logic and private function(s) that Directory already implements/uses.


Please don’t reply on this GitHub thread. Visit golang.org/cl/171577.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link

Message from Anton Antonov:

Patch Set 1: Code-Review+1

Patch Set 1:

A bit more rationale:

Since go1.12 enhanced further the ReverseProxy implementation a closed source library (and many more open-source ones) that provide a reverse proxy for HTTP and WS can be deprecated.

The only difference between the closed source library was that I had a more convenient hook to modify a request that allowed me to focus only on the VHOST logic.

The change here would noticeably reduce the boilerplate and make developers avoid re-implementing logic and private function(s) that Directory already implements/uses.


Please don’t reply on this GitHub thread. Visit golang.org/cl/171577.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link

Message from Agniva De Sarker:

Patch Set 1:

Patch Set 1:

A bit more rationale:

Since go1.12 enhanced further the ReverseProxy implementation a closed source library (and many more open-source ones) that provide a reverse proxy for HTTP and WS can be deprecated.

The only difference between the closed source library was that I had a more convenient hook to modify a request that allowed me to focus only on the VHOST logic.

The change here would noticeably reduce the boilerplate and make developers avoid re-implementing logic and private function(s) that Directory already implements/uses.

Hi Anton, please open an issue on github so that we can discuss this further. Any public API addition should have an attached issue with it, and be approved before we can start looking into the implementation.

Thanks.


Please don’t reply on this GitHub thread. Visit golang.org/cl/171577.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link

This PR (HEAD: 7311c0f) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/go/+/171577 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@bradfitz bradfitz changed the title httputil: add ModifyRequest hook net/http/httputil: add ReverseProxy.ModifyRequest Apr 11, 2019
@syndbg syndbg changed the title net/http/httputil: add ReverseProxy.ModifyRequest documentation: net/http/httputil: add example for reuse of Director Apr 15, 2019
@syndbg syndbg force-pushed the add-modify-request-hook branch 3 times, most recently from 49e94da to 349c6e7 Compare April 15, 2019 20:22
@syndbg syndbg closed this Apr 15, 2019
@syndbg syndbg deleted the add-modify-request-hook branch April 15, 2019 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Used by googlebot to label PRs as having a valid CLA. The text of this label should not change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants