Hi everyone.

I have this problem that I am experiencing when I move a certain site from one hosting to another hosting location. This is why I think this problem is not related to ASP code, rather than to IIS settings which are different in one hosting company to another.

I am talking about a site I have that has no pages on it, rather it catches 404 http errors and according to the filename of the missing page, it returns content to browser. Now, on some hosting companies, I see for requested missing .asp pages ONLY (i.e: for missing .html files it works great on all hosting locations) that in the address bar of the browser I see something like:

http://www.site.com/404.asp?404;http://www.site.com/sample.asp

when I request the page - http://www.site.com/sample.asp

When I move this site to another hosting company, maybe due to different IIS settings, I see in the address bar this address:

http://www.site.com/sample.asp

which is how it should be.

My question is this: How do I set IIS or change ASP code so that on the hosting locations where the address bar is showing the URL as http://www.site.com/404.asp?404;http://www.site.com/sample.asp for missing http://www.site.com/sample.asp page, I will simply see http://www.site.com/sample.asp as if the page exists on site ??

NOTE that with missing .html pages all is working well on all hosting location/IIS servers.

Thanks for the help!
Sami

Sounds like your first host has put in a custom 404 error page to trap the errors...or you did.

Remove the custom 404 off of the first host and you'll be fine.

Hi Adam web design,

Thanks a lot for your quick and concise reply. I went through it and removed the /404.asp entry as the 404 error handling script from the host that shows in the address bar something like this - http://www.site.com/404.asp?404;http://www.site.com/sample.asp but then the whole site was not functioning and I got error 404 for all missing pages. Do you know what can be done?

Thanks a lot!

Okay, so you do have a custom 404 page...which is probably what you wanted. You will get the 404 error with it removed because...well...the pages are missing, and that's the result you're supposed to get. That's normal, expected, and correct behaviour.

I've seen the same behaviour with a custom 404, and never did find the answer to it. In the end, I just chose to ignore it...it really doesn't have an impact on anything.

it will depend on if the custom 404 type is set to URL or file

to use a scripted 404 page it should be set to URL, note that using a scripted page the response returned to user agents will be a 200 NOT a 404, make sure your script returns the correct response appropriately to UAs