Re: IGNORABLE_404 woes

[Karen Tracey]

On Sat, Sep 26, 2009 at 11:33 PM, troyhitch  wrote:

>
> I think I may have figured out what was happening. I did not have a
> 404.html in templates, and assume now that the messages were coming
> only because of that (the missing template seemed consequential to me
> and not the primary cause). I didn't think a template was necessary.
> Can someone confirm that this is the case?
>
>
Assuming you are using the default error handlers, you do need a 404.html
template.  Without it the server will wind up raising an exception when it
tries to return a 404 response.

I guess, then, you were not actually getting broken link emails (which have
a subject like Broken INTERNAL link on [site] and a body showing the
referrer, the requested URL, the user agent, and the IP address of the
requestor) but rather server error emails (which have a subject of ERROR
along with the requested URL and have a body that shows the traceback of the
error)?  I don't see how you could have been getting broken link emails if
you did not have a 404.html template.

You do also need a 500.html template.

Karen

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: IGNORABLE_404 woes

[Graham Dumpleton]

On Sep 27, 1:15 am, troyhitch  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
-~--~~~~--~~--~--~---

Re: IGNORABLE_404 woes

[troyhitch]

I think I may have figured out what was happening. I did not have a
404.html in templates, and assume now that the messages were coming
only because of that (the missing template seemed consequential to me
and not the primary cause). I didn't think a template was necessary.
Can someone confirm that this is the case?

Thanks,
Troy

On Sep 26, 5:14 pm, Karen Tracey  wrote:
> On Sat, Sep 26, 2009 at 4:41 PM, troyhitch  wrote:
>
> > Michael -
>
> > Thanks. Unfortunately this doesn't seem to have solved the problem. I
> > updated settings.py on the culprit site with this:
>
> > IGNORABLE_404_STARTS = ('/cgi-bin/',)
> > IGNORABLE_404_ENDS =
> > ('favicon.ico','favicon.ico/','.php','.php/','robots.txt','robots.txt/')
>
> > But continue to see the same 404 warnings. I'm happy to file a bug,
> > but I'm still vexed as to why it would be working fine on the sister
> > site.
>
> What's the referring page for these listed as?  Checking my logs I don't
> ever see these things coming in with a referrer set, meaning they wouldn't
> generate broken links email.  I'm curious why you are seeing these come in
> (apparently) with referrers.
>
> Karen
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: IGNORABLE_404 woes

[Karen Tracey]

On Sat, Sep 26, 2009 at 4:41 PM, troyhitch  wrote:

>
> Michael -
>
> Thanks. Unfortunately this doesn't seem to have solved the problem. I
> updated settings.py on the culprit site with this:
>
> IGNORABLE_404_STARTS = ('/cgi-bin/',)
> IGNORABLE_404_ENDS =
> ('favicon.ico','favicon.ico/','.php','.php/','robots.txt','robots.txt/')
>
> But continue to see the same 404 warnings. I'm happy to file a bug,
> but I'm still vexed as to why it would be working fine on the sister
> site.
>
>
What's the referring page for these listed as?  Checking my logs I don't
ever see these things coming in with a referrer set, meaning they wouldn't
generate broken links email.  I'm curious why you are seeing these come in
(apparently) with referrers.

Karen

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: IGNORABLE_404 woes

[troyhitch]

Michael -

Thanks. Unfortunately this doesn't seem to have solved the problem. I
updated settings.py on the culprit site with this:

IGNORABLE_404_STARTS = ('/cgi-bin/',)
IGNORABLE_404_ENDS =
('favicon.ico','favicon.ico/','.php','.php/','robots.txt','robots.txt/')

But continue to see the same 404 warnings. I'm happy to file a bug,
but I'm still vexed as to why it would be working fine on the sister
site.

Thanks again,
Troy

On Sep 26, 11:32 am, Michael  wrote:
> On Sat, Sep 26, 2009 at 11:15 AM, troyhitch  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?
>
> > Thanks,
> > Troy
>
> The ignorable 404s only include the urls without the trailing slash. When
> you have the APPEND_SLASH setting on in django(by default) the request to
> robots.txt is redirected to robots.txt/. You'll have to add that url to the
> Ingorable_404 something. I have been debating about filing this into trac as
> a bug. If you decide to, please include the ticket number here.
>
> Thanks,
>
> Michael
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: IGNORABLE_404 woes

[Michael]

On Sat, Sep 26, 2009 at 11:15 AM, troyhitch  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?
>
> Thanks,
> Troy
>

The ignorable 404s only include the urls without the trailing slash. When
you have the APPEND_SLASH setting on in django(by default) the request to
robots.txt is redirected to robots.txt/. You'll have to add that url to the
Ingorable_404 something. I have been debating about filing this into trac as
a bug. If you decide to, please include the ticket number here.

Thanks,

Michael

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

IGNORABLE_404 woes

[troyhitch]

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?

Thanks,
Troy
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---