This repository was archived by the owner on Apr 22, 2023. It is now read-only.
Support for HTTP raw headers #259
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I wish that this could be reconsidered for implementation (or at least something very similar). I am working on something that will need to do a reverse proxy request in some cases. It would be nice to be able to simply pipe the ClientResponse headers into the ServerResponse headers somehow. Currently you have to deal with two conversions:
Sstephenson's would fix this in a pretty graceful way (I think). |
This pull request was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds support for HTTP raw headers, as described in this mailing list thread. Useful when building reverse proxy servers.