#34465: Handle malformed CSRF cookie
---------------------------------+--------------------------------------
Reporter: Miha Sedej | Owner: nobody
Type: Bug | Status: closed
Component: CSRF | Version: 4.1
Severity: Normal | Resolution: needsinfo
Keywords: csrf, 500 error | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => needsinfo
Comment:
`CsrfViewMiddleware` already
[https://github.com/django/django/blob/73cbb372baa45d1fdafd571e2f430a980831f722/django/middleware/csrf.py#L129-L139
rejects] tokens with invalid length or characters. Can you provide a small
reproducible scenario?
--
Ticket URL: <https://code.djangoproject.com/ticket/34465#comment:2>
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/010701875abd7755-83a19f06-97b9-4c60-a7cc-9156bbef6442-000000%40eu-central-1.amazonses.com.
