feat: Per-request redirect policy override #2440
Open
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
ref: seanmonstar#1204 co-authored-by: Greg Kuruc <[email protected]>
mikayla-maki
changed the title
mikayla-maki
changed the title
mikayla-maki
force-pushed
the
0.12.8-per-request-redirect
branch
from
6f88db0 to
fd110f6
Compare
|
I would need this PR also for my project, don't know about the priority but it would be nice if this could be added! |
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.
This is a repeat of #1204, with minimal changes.
Fixes #353
At Zed, our previous HTTP client exposed an API for configuring the redirect policy per-request configuration. We've since used this feature in a few places, as well as exposed it via our extension API. We're now working on upgrading our HTTP client to
reqwestand so would like to revive and take responsibility for this old PR!