-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Should we do 303 redirects upon form submit? #1433
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
Comments
@Arkounay sorry for the late reply. Thanks for creating this detailed issue. Yes, I think it would make sense to do this change. Would you have some time to create a Pull Request with this change? If you don't have time for it, we'll ask others in the community to contribute this. Thanks. |
@javiereguiluz No problem thanks for the reply, yes I can create a pull request next week 👍 |
Arkounay
added a commit
to Arkounay/symfony-demo
that referenced
this issue
Nov 6, 2023
Merged
javiereguiluz
added a commit
to javiereguiluz/demo
that referenced
this issue
Nov 8, 2023
This PR was merged into the main branch. Discussion ---------- 303 redirections This PR provides 303 redirections, see issue symfony#1433 Commits ------- bc55637 303 redirections symfony#1433
Closing as fixed in #1448. |
muqeetsyed
pushed a commit
to muqeetsyed/docker-symfony
that referenced
this issue
Dec 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I create a CRUD with
php bin/console make:crud
, when a form is submitted there will be a 303 redirection:in symfony-demo, it's the default redirection (which is 302) that is used:
demo/src/Controller/Admin/BlogController.php
Line 110 in 7e6cc8f
303 seems like a better practice:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/303
While it seems 302 is recommended only for GET or HEAD methods:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/302
It's not super important but is it a better practice to use 303? Should the code be changed to reflect that?
The text was updated successfully, but these errors were encountered: