#32795: Reject requests earlier if the non-cookie CSRF token is missing or has
the
wrong format
-------------------------------------+-------------------------------------
Reporter: Chris Jerdonek | Owner: Chris
Type: | Jerdonek
Cleanup/optimization | Status: assigned
Component: CSRF | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"ffdee8d2645227748ae4061f21fc48cca4d75c22" ffdee8d2]:
{{{
#!CommitTicketReference repository=""
revision="ffdee8d2645227748ae4061f21fc48cca4d75c22"
Refs #32795 -- Added CsrfViewMiddleware tests for rejecting invalid or
missing tokens.
This also improves test names for test_process_request_no_csrf_cookie
and test_process_request_csrf_cookie_no_token. The logic being tested
is actually in process_view() rather than process_request(), and it's
not necessary to include the method name.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32795#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.866e6fd2ef5e80dbe4665df3fe8d3654%40djangoproject.com.
