Location header rewriting for responses with status 201 #1024
Conversation
This file contains 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
Implement rewriting of the location header for responses with status code 201, according to RFC2616 section 10.2.2
|
@gabrielboucher seems reasonable to me if its in the spec. Thanks for the contribution! Would you mind adding a test for the |
|
The test is already there |
|
ha, looking too quickly. thanks for keeping me on my toes :) |
smh
added a commit
to smh/node-http-proxy
that referenced
this pull request
Mar 4, 2017
Updates options documentation for location rewrite to include 201 responses. See http-party#1024
indexzero
pushed a commit
that referenced
this pull request
Aug 22, 2019
Updates options documentation for location rewrite to include 201 responses. See #1024
mcheshkov
pushed a commit
to gemini-testing/node-http-proxy
that referenced
this pull request
Sep 16, 2019
Updates options documentation for location rewrite to include 201 responses. See http-party#1024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Implement rewriting of the location header for responses with status code 201, according to RFC2616 section 10.2.2, in response to issue #914