on CRSF failure respond with 400 instead of 500
with an invalid CSRF-Token symfony responds currently with an 500 status code, which is the wrong status code for that https://sentry.io/foodsaving-worldwide/foodsharingde-beta/issues/897394886/
How confident are you it won't break things if deployed?
absolutely
Links to related issues
Checklist
- [-] added a test, or explain why one is not needed/possible...
-
no unrelated changes -
asked someone for a code review -
joined #foodsharing-beta channel at https://slackin.yunity.org - [-] added an entry to CHANGELOG.md (description, merge request link, username(s))