#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       |               Resolution:
     Keywords:               |             Triage Stage:  Unreviewed
    Has patch:  0            |      Needs documentation:  0
  Needs tests:  0            |  Patch needs improvement:  0
Easy pickings:  0            |                    UI/UX:  0
-----------------------------+--------------------------------------
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 405 errors are an order of magnitude less common than 404 and 403.

 I don't think it's a good idea to keep adding exception classes and
 hardcoding handlerXXX in URLconfs. We should start thinking about a more
 generic mechanism.

 For instance we could have a view to deal with client errors (4XX), a view
 for server errors (5XX), and pass adequate arguments to these views. But
 that would create lots of code churn in existing projects :/

-- 
Ticket URL: <https://code.djangoproject.com/ticket/22058#comment:1>
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/067.7dfb5ea3e34a513e5abaccb545025434%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to