#26146: CsrfViewMiddleware responds to any arbitrary HTTP method outside of
'GET',
'HEAD', 'OPTIONS', and 'TRACE'
-------------------------------------+-------------------------------------
Reporter: finetype | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: CSRF | Version: 1.8
Severity: Normal | Resolution:
Keywords: trace, track, csrf, | Triage Stage: Accepted
error, page |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by carljm):
I don't see why it's the CSRF middleware's responsibility to return a 405
or 400 in case of an HTTP verb it doesn't recognize. That seems out of
scope for the CSRF middleware. It should exempt known-safe verbs, and
assume everything else needs protection. Which is exactly what it does
now.
If you want unknown verbs to be unconditionally rejected with a 405, just
write a middleware to do that.
I don't see how a new middleware rejecting unknown verbs with 405 would
"clash" with `.dispatch()` any more than having CSRF middleware reject
them with 405 would.
I still don't see anything that needs changing here.
--
Ticket URL: <https://code.djangoproject.com/ticket/26146#comment:4>
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/066.ee30fe0418ac4e4432ab10baa5c770ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
