I see... I was doing some testing using header checker tools and you are right, they all show 404 except for the tool at webmasterworld... I was trying to figure out why they showed a 200. It appears that google is seeing the 404s, though... That is what I was concerned about.
Just as an aside, Gbot is doing some creative crawling and adding in various numbers and words In queries to try to mine data that normally users wouldn't find. Others have noted this same problem. Whether G thinks it is a problem or not, remains to be seen. This has caused a bit of a problem with one of my sites. An example... <@APPFILE>?a=111&b=222&c=3 - this would be my normal query... Googlebot is inserting random numbers and rearranging the order of the queries. The c value is not necessary to return the page (it is now, though). So I show in the logs... <@APPFILE>?b=222&a=111&c=8 <@APPFILE>?c=9&a=111&b=222 <@APPFILE>?a=111&c=10&b=222 All pointing to the same content. Currently this created over 6600 duplicate pages in the SERPs. I am trying to get this straightened out via robots.txt, no-follows, ISAPI and cleaning up the code. What next, eh? -----Original Message----- From: Scott Cadillac [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2008 12:10 PM To: [email protected] Subject: Re: Witango-Talk: Revisiting http headers Hey Dude, Remember, IIS handles the request before Tango does, so technically speaking IIS did find your page, otherwise the TAF would not have executed your code. What counts is that the browser got a 404 response from the server. Hope that helps. Scott, On Jul-1-2008, at 1:21 PM, WebDude wrote: > I understand that when I assign this to the "not found" file, it works > correctly when the actual file does not exist. However, is it possible > to get this to work on a no results page? I tried this at the head of > a no results page, yet IIS5 logs show it as being found. > Any way around this? This is what I have... > > <@purgeresults><@assign httpheader "HTTP/1.0 404 Not > Found<@CRLF><@CRLF>" scope=local> > > Thanks! > > > ______________________________________________________________________ > __ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
