Custom 400 error handler or capture broken URLs

[Simon Steinberger]

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.

[Karen Tracey]

There is a ticket open on this issue:

https://code.djangoproject.com/ticket/19508

[Simon Steinberger]

Excellent - thank you!

[Loic Bistuer]

Hi Simon,

I’ve updated the ticket with a new PR, would you mind giving it a try?

Thanks

--
Loic

> --
> 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-develop...@googlegroups.com.
> To post to this group, send email to django-d...@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.