CXF-8746: Support force GET on redirections #977
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
|
@ypiel-talend my apologies, I have difficulties to understand this change, the sections you are referring to note that:
This is the behavior driven by user agent (client) and not the server, I am not sure why CXF needs change here. Also, seems like this is really outdated behavior (from notes on spec), why do we need to support it? What is the use case? Thank you. |
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.
CXF-8746: Support force GET on 301 & 302 redirections for historical reasons as explained in https://www.rfc-editor.org/rfc/rfc7231.html section 6.4.2 & 6.4.3.