#22058: Add `Http405` exception class and `handler405` view (simillar to 404,
403
and 500)
-----------------------------+--------------------
Reporter: debanshuk | Owner: nobody
Type: New feature | Status: new
Component: Core (URLs) | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------
With class based views it's not straight forward to to raise a `Http404`
error if the view doesn't support HTTP method (i.e. a 405 error), with
function based views it was. So, in such cases clients (users) see a blank
page with 405 response code, but with no message to tell them where to go
from there. I guess Django should raise and handle `Http405` exception and
use a default `handler405` view (which of course can be overridden) to
return response to user in such a case, as it does in case of 404, 403 and
500 errors.
--
Ticket URL: <https://code.djangoproject.com/ticket/22058>
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/052.e397ab5174ad0a930bdbaf0f5a7db455%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
