HTTPCLIENT-2390: introduce RedirectMethodPolicy to control 301/302 method rewriting. #713
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
…ewriting. Opt-in preservation of POST (repeatable entity) while keeping the browser-compatible default; classic and async updated with tests and examples.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
y default the client remains browser-compatible; when requested, POST (with repeatable entity) is preserved across 301/302, while 303 continues to use GET and 307/308 remain method-preserving. Classic and async execution chains updated, with DEBUG traces explaining branch decisions, new examples for classic/async, and unit tests covering preservation and defaults. Behavior is unchanged for existing users unless the new policy is explicitly enabled.