Hi,
Check both the Querystring and the current page name. Depending on whether
the file was handler by the IIS Static File Handler, or handled by an ISAPI
filter, you will see different results in the browser's address bar. This is
a function of whether IIS is internally using something akin to
Server.Execute to transfer across to the 404 page, or is using something
akin to Response.Redirect() to transfer across to the 404 page.
Cheers
Ken
"Greg Collins [Microsoft MVP]" <gcollins_AT_msn_DOT_com> wrote in message
If you are using the web.config error redirecting, you get a partial url
listed in the query string under aspxerrorpath=/path (except that if in this
case all the original query string parameters are lopped off and you only
get the path to the page -- not as useful as it could be).
In my case, I'm referring to going into the IIS settings and modifying the
pointer to the default 404 error page to a custom page. In this case the
browser address well still shows the address that cased the 404 error (as it
was typed in or navigated to), but the custom 404 page displays. No
modification is made to the url.
It is in this latter case that I want to be able to identify the url in the
address well that was sent to my custom 404 page (again this is from an IIS
modification, not a web.config setting).