Author: fredman | Posted on: 6/12/2010 5:48:19 AM | Views : 228

Hi,

My web app is on shared server, so I only have limited things i do on the server level. However, I can set up a custom error page.

Catching 404 errors is easy if the requested URL is for a (non-existent) aspx page, but if the user requests a non-existent HTML page hgow can I catch this error, have it redirected to my custom error (aspx) where I can process their request and hopefully redirect them to where they wanted to go?
I can't do anything in web.config or global.asax as the server catches the 404 and redirects them before the request ever gets that far. As I said though, my web host allows me to create a (global) custom error page, (error.aspx) but what I need now is a way to find the originally requested URL....  I don't know php, but Googling has revealed that php seems to have a REQUEST_URI that returns this, but I can't see any equivalent in ASP's Request ServerVariables collection. Neither PATH_INFO nor ...

Go to the complete details ...