Download
2011-02-03, 15:50:32
Yes, I already did that (it's the bug fix I mention in my first post).
[Later] README for hosted sites.
If you use a hosting company for your site, you may come across the problem I described. In summary, the cause is inaccurate logging. There is no bug in GS (apart from the one I mention above).
The issue was that I was checking my logs and noticed that a path I knew was invalid was returning a 200. I also knew that Google frown on incorrect 200 for SEO, so I wanted to fix it.
I then went into a long, convoluted and pointless testing session to try and find why GS wasn't returning a 404 for invalid paths.
Eventually, I telnet'ed into the server and was able to see the exact output. Lo and behold, GS was returning a 404. So, GS is doing the correct thing.
I still don't know exactly what is happening. I think that my hosting company's apache logs are not correct. The 404 is not showing in either the access.log or the error.log.
My hosting company is DreamHosti. I wonder what other DreamHost customers are seeing in their logs.
[Later] README for hosted sites.
If you use a hosting company for your site, you may come across the problem I described. In summary, the cause is inaccurate logging. There is no bug in GS (apart from the one I mention above).
The issue was that I was checking my logs and noticed that a path I knew was invalid was returning a 200. I also knew that Google frown on incorrect 200 for SEO, so I wanted to fix it.
I then went into a long, convoluted and pointless testing session to try and find why GS wasn't returning a 404 for invalid paths.
Eventually, I telnet'ed into the server and was able to see the exact output. Lo and behold, GS was returning a 404. So, GS is doing the correct thing.
I still don't know exactly what is happening. I think that my hosting company's apache logs are not correct. The 404 is not showing in either the access.log or the error.log.
My hosting company is DreamHosti. I wonder what other DreamHost customers are seeing in their logs.
My blog: http://www.nickcoleman.org/blog
