Re: [Django] #22058: Add `Http405` exception class and `handler405` view (simillar to 404, 403 and 500)

[Django]

#22058: Add `Http405` exception class and `handler405` view (simillar to 404, 
403
and 500)
-+---
 Reporter:  debanshuk|Owner:  anubhav9042
 Type:  New feature  |   Status:  assigned
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 anubhav9042):

 * status:  new => assigned
 * owner:  nobody => anubhav9042
 * cc: anubhav9042@… (added)


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.fe98f6164f789e43ccba301321a51dd3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22058: Add `Http405` exception class and `handler405` view (simillar to 404, 403 and 500)

[Django]

#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
-+--

Comment (by anubhav9042):

 I am interested in this especially I want this to incorporate in GSoC
 proposal.
 As suggested we can just have two views which can be matched with regex
 4XX and 5XX, and accordingly lot of code will be reduced.
 Also as this ticket suggests, we can add some more cases including 405
 like 401, etc

 Any suggestions??

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.6e5739a088ce52ab22cc520a9ebf1230%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22058: Add `Http405` exception class and `handler405` view (simillar to 404, 403 and 500)

[Django]

#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: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
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.

[Django] #22058: Add `Http405` exception class and `handler405` view (simillar to 404, 403 and 500)

[Django]

#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: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
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.