Support status codes for redirects #717
Merged
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
|
Good change! Let's add |
|
dzucconi
force-pushed
the
feat/support-status-in-redirect
branch
2 times, most recently
from
0ece0b7
to
20b4e65
Compare
dzucconi
force-pushed
the
feat/support-status-in-redirect
branch
from
20b4e65
to
faa39c1
Compare
|
@taion 👍 updated |
|
Pushed a little commit to add |
|
published in v0.5.5 |
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.
Seems like it would make sense to be able to also support an optional status code on the error.
My use-case here is wanting to have some server-side redirects be permanent (301) and being able to differentiate.