On Thursday, July 14, 2005, at 10:44 AM, [EMAIL PROTECTED] wrote:

Hi Bill,

Thanks for answering.

A question or two if you please...

I am running IIS5 on a Win2k server. In order to do redirects, the files have to already exist. I was hoping for something a bit more elegant then this. We are talking of hundreds of files.


Don't know IIS. Apache mod_rewrite allow regular expression pattern matching so you can do many at once. You should take a look at the apache docs anyway because they show lots of ways of handling the situation. You might get some ideas.

What I am looking for is whether it is possible to have the server return the proper 404 rather then Witango when the application file is missing. Not sure if this can be done.


Again, apache lets you intercept this before dispatching to the handler (witango in this case). I presume there are ISAPI filters to do this.

When you say "... have your witango error handler send the appropriate code," I am not sure what you mean nor how to do this. I am wondering if anyone has attempted this before in Windoze and what steps I need to take to return proper headers when files aren't found.


Or have Witango manage it.  In your error handler:

if mainerror = 3 {
        if requested file is in list of old files {
<@PURGERESULTS><@ASSIGN SCOPE="request" NAME="httpheader" VALUE="HTTP/1.1 404 Not Found<@crlf> <@crlf>">
                return action
        }
else {
        continue with error handler
}



Thanks!



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

_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf


________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to