-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
set correct http status code in redirect response #22497
Conversation
Was intended to respond with a 303 (See other) status code instead of 307 (Temporary Redirect).
By analyzing the blame information on this pull request, we identified @DeepDiver1975, @MorrisJobke and @BernhardPosselt to be potential reviewers |
You need to adjust the unit test as well, when you did that, please set the label "To Review" |
As discussed yesterday on IRC 👍 if unit tests are fixed. Background: This response was intended to implement the Post/Redirect/Get pattern: https://en.wikipedia.org/wiki/Post/Redirect/Get |
👍 |
Fine by me. 👍 |
set correct http status code in redirect response
This kind of breaking changes has to be advertised on the devel mailing lists. |
Well basically can happen with any function that is changed. |
Yes and all such changes should be advertised. We're not talking about private APIs here. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Was intended to respond with a 303 (See other) status code instead of 307 (Temporary Redirect).
cc @BernhardPosselt (btw: thanks for the fix! ;))