Custom 400 error handler or capture broken URLs

134 views
Skip to first unread message

Simon Steinberger

unread,
Oct 8, 2014, 7:39:59 PM10/8/14
to django-d...@googlegroups.com
Django sites respond to broken URLs with a blank error 400 page. E.g. here on Disqus:


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:


Would be nice to be able to catch this error in a more Django-friendly way.

Karen Tracey

unread,
Oct 10, 2014, 10:00:33 AM10/10/14
to django-d...@googlegroups.com
There is a ticket open on this issue:

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

Simon Steinberger

unread,
Oct 13, 2014, 2:27:55 AM10/13/14
to django-d...@googlegroups.com
Excellent - thank you!

Loic Bistuer

unread,
Oct 13, 2014, 4:35:25 AM10/13/14
to django-d...@googlegroups.com
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.

Reply all
Reply to author
Forward
0 new messages