#33529: Possibly Incorrect statement in the docs about CRSF tokens
------------------------------+--------------------------------------
Reporter: Michael | Owner: nobody
Type: Bug | Status: closed
Component: contrib.auth | Version: 4.0
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Comment (by Michael):
Replying to [comment:2 Florian Apolloner]:
> I honestly have no idea what the note is trying to say. The
`CsrfViewMiddleware` has no access to the DOM after all :D What do I miss?
CSRF token that is POSTed, which the middleware sees, originates from a
CSRF token that is embedded in the DOM (usually via a `{% csrftoken %}`,
as noted in the orginal post).
--
Ticket URL: <https://code.djangoproject.com/ticket/33529#comment:5>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.453f4b84353adb8a01c87064820c0417%40djangoproject.com.
