On Sep 27, 1:15 am, troyhitch <troyhi...@gmail.com> wrote:
> Hi everyone -
>
> I have deployed two django sites on the same server, with identical
> configs (apache, mod_wsgi) and have added this to each of their
> settings.py:
>
> IGNORABLE_404_STARTS = ('/cgi-bin/',)
> IGNORABLE_404_ENDS = ('favicon.ico','.php','robots.txt')
>
> It works perfectly for one site, but not at all for the other. I'm
> still getting deluged with /favicon.ico and robots.txt 404 emails: but
> for only one of the sites. I'm not overriding anything in a local
> settings file. Am I missing something server side? Or maybe even DNS-
> wise?
Why aren't you blocking these or mapping them to real static files in
the Apache web server configuration itself? The mod_wsgi documentation
gives examples of how to have Apache handle them as static files. See:
http://code.google.com/p/modwsgi/wiki/ConfigurationGuidelines#Hosting_Of_Static_Files
If the target of the URL is missing, then Apache will send its own 404
so long as you haven't overridden ErrorDocument for 404 to map to a
URL which would then be handled by Django.
Graham
Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
