For the record, I used this to turn the 500 errors into 404's - which makes the severity of the ticket a bit lower as it's reasonably easy to work around the 500 email spam associated issue: RewriteRule .*\.(gif|ico|jpe?g|bmp|wmf|mid|rmi|rm|ram|au|wav|art|img)$ - [L,NC]
Lakin On Oct 21, 8:19 am, Lakin Wecker <lakin.wec...@gmail.com> wrote: > http://code.djangoproject.com/ticket/11967 > > As commented on the ticket: > > This is driving me nuts too. It wouldn't be so bad if this was a 404, but > combined with #11191 and #3785 it generates a ton of 500 errors. :/ > > Any chance this will be in 1.0.5 or 1.1.2? I mean - I can configure > apache to treat this url as a 404 - and stop the 500 errors, but the > fact that by default it generates 500 errors makes me think this is > something that's important to get into a release. (Maybe along with > the patch on #11191). > > Lakin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
