Re: Custom 400 error handler or capture broken URLs
Excellent - thank you! On Friday, October 10, 2014 4:00:33 PM UTC+2, Karen Tracey wrote: > > There is a ticket open on this issue: > > https://code.djangoproject.com/ticket/19508 > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/04b02c02-3504-4702-9765-4ad51ab83b85%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Custom 400 error handler or capture broken URLs
Django sites respond to broken URLs with a blank error 400 page. E.g. here on Disqus: http://disqus.com/%C3A4 This error is raised inside the WSGI application and currently there's no way to avoid it or to use some custom error 400 page. We do have a nasty patch that's grossly inefficient and ugly: http://stackoverflow.com/questions/14636986/catch-incorrectly-encoded-urls-in-django-to-return-a-custom-error-400-page/14682988#14682988 Would be nice to be able to catch this error in a more Django-friendly way. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4e1941f9-70f8-4357-b19c-933ddc5adfe3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
