CSRF error when adding activity
See original GitHub issueWhen I try to create a new activity, after filling the fields and pressing the ‘Submit’ button, the error ‘CSRF Failed: CSRF cookie not set.’ is displayed.
I tried to execute the same procedure on production environment (speakerfight.com) and got the same error.
Exact steps to reproduce:
- Login into speakerfight
- Click
New Event
- Fill the form and submit
- Click
Create Schedule
- Cllick
Add Activity
- Fill the form and submit
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
csrf error in django - python - Stack Overflow
I was having the exact same issue - and Blue Peppers' answer got me on the right track. Adding a RequestContext to your...
Read more >CSRF token error messages - Todoist
This error message means that your browser couldn't create a secure cookie, or couldn't access that cookie to authorize your login. This can...
Read more >Cross Site Request Forgery (CSRF) - OWASP Foundation
Cross-Site Request Forgery (CSRF) is an attack that forces an end user to execute unwanted actions on a web application in which they're...
Read more >While using TOKEN I am getting CSRF errors when trying to ...
One curious bit of info, I just noticed that when I do use the tc-csrf-token parameter to pass the request, the error goes...
Read more >A missing or invalid CSRF token was found? - Forums - IBM
In the qradar.error logs following errors are generating for this activity. Feb 1 10:24:29 x.x.x.x [tomcat] [abc@y.y.y.y (9276) ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After #182 , we realized that CsrfViewMiddleware is disabled.
This bug happens because DRF is not ignoring the CSRF token check.
Should we enable the CsrfViewMiddleware?
@mazulo , did you replicate this issue? i believe this should be solved by now.