#26165: Add an FAQ that explains why Django's CSRF isn't vulnerable
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: acemaster
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"73d8e646d743aad79d6067ae3d8facf83b1e76a4" 73d8e646]:
{{{
#!CommitTicketReference repository=""
revision="73d8e646d743aad79d6067ae3d8facf83b1e76a4"
[1.9.x] Fixed #26165 -- Added some FAQs about CSRF protection.
Thanks Florian Apolloner and Shai Berger for review.
Backport of a1b1688c7d6c1a6d307bd22669bd20f08e948f8d from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26165#comment:8>
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/067.4406fcd3f7a80103e15522bfbaa29ba8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
