Re: Custom 400 error handler or capture broken URLs

Hi Simon, I've updated the ticket with a new PR, would you mind giving it a try? Thanks -- Loic On Oct 13, 2014, at 1:27 PM, Simon Steinberger wrote: > Excellent - thank you! > > On Friday, October 10, 2014 4:00:33 PM UTC+2, Karen Tracey wrote: > There is a ticket open

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

Re: Custom 400 error handler or capture broken URLs

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

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