#26165: Add an FAQ that explains why Django's CSRF isn't vulnerable
------------------------------------------------+------------------------
Reporter: timgraham | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
It's a common invalid report to the security mailing list.
There are some public threads like https://groups.google.com/d/topic
/django-developers/zpqGUyAdjH8/discussion but it would nice to be have a
canonical answer to point to.
--
Ticket URL: <https://code.djangoproject.com/ticket/26165>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.42bf9729d19387a77a0ce1de93614cd1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
