#26165: Add an FAQ that explains why Django's CSRF isn't vulnerable
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: acemaster
Type: | Status: assigned
Cleanup/optimization |
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* has_patch: 0 => 1
* stage: Ready for checkin => Accepted
Comment:
Please don't mark your own ticket as "Ready for checkin" -- see the
[https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
tickets/ triaging guidelines].
I created a [https://github.com/django/django/pull/6081 pull request] from
your branch..
--
Ticket URL: <https://code.djangoproject.com/ticket/26165#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.af7326059e751d2a42382e44e602bd71%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
