Per route CSRF #1

Open
opened 2018-11-01 14:51:22 +00:00 by JohnMidity · 0 comments
JohnMidity commented 2018-11-01 14:51:22 +00:00 (Migrated from github.com)

Because in the current setup the CSRF is running on all routes, it is not possible to call the API. To solve this, a per-route CSRF should be made possible and then the CSRF can be off for API routes.

Because in the current setup the CSRF is running on all routes, it is not possible to call the API. To solve this, a per-route CSRF should be made possible and then the CSRF can be off for API routes.
This discussion has been locked. Commenting is limited to contributors.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
John/Snugger#1
No description provided.