Presumably you have an error trap for Witango Main Error 3 (file not
found) that displays your error page. The error page is a valid page
so it should return 200 OK.
You need to have your web server return a 404 Not Found, 302 Redirect,
or 301 Moved in response to these requests, before the Witango error
handler is invoked. See apache mod_rewrite.
Or have your witango error handler send the appropriate code.
bill
On Thursday, July 14, 2005, at 08:18 AM, [EMAIL PROTECTED]
wrote:
I know this has come up before, but I need a little help.
I redid a site and all the taf file names have been changed. I wanted
to use the Google URL removal tool to get rid of the old taf files.
They are still being crawled by Google but all the links end up
pointing to the default Witango error page. In fact, after years of
using Witango, I have noticed that Google will keep crawling these
pages because, according to Google, they still exist and return as 200
Object Found pages. On 40 websites, I have many of these links that
are still being indexed by Google and I want to clean up all the sites
and remove the dead URLS. Google requests that all pages listed for
removal be a 404 page. In otherwords, a true Object Not Found page. I
did a header check on one of the dead URLs and have found that Witango
treats the error page as a 200 Object Found. Is there any way to
change the header info and have Witango treat these pages as a 404
pages? Eventually, Google will drop them if I could figure this one
out.
Thanks.
_______________________________________________________________________
_
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf