#25822: Create require_HEAD, require_OPTIONS, require_PUT, etc. in
django.views.decorators.http
-----------------------------+---------------------------------------
Reporter: CrazyPython | Owner: CrazyPython
Type: New feature | Status: assigned
Component: Utilities | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-----------------------------+---------------------------------------
Comment (by aaugustin):
Since browsers don't do anything other than GET and POST and since APIs
are usually built on top of frameworks (DRF, or even just Django class
based views) which have better APIs for enforcing such restrictions, I
don't believe this is useful. The "consistency" argument isn't enough for
convincing me.
--
Ticket URL: <https://code.djangoproject.com/ticket/25822#comment:6>
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/069.6655bf50d70b600daab1197161c30e3e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
