global.aspx Application_error does not fire on anything other than

[jvcoach23]

ahh.. the server.transfer is not happing at the client...if i were to do a
resposne.redirect, then that would actaully bring up the page url, cause
the client is the one issing the request... that more on track?

 

[Juan T. Llibre]

re:
!> I republished and now i click on the dead link and the address bar shows
!> the dead link url, but the message on the screen is

!> The page you have requested can't be found.
!> We're sorry for the inconvenience.

If that's the case, both global.asax and Application_Error are firing.

re:
!> but the url is the dead link... does that sound correct.

Yes. Server.Transfer preserves the original link.
Errors.aspx will *not* show up on the address bar.

 

[Juan T. Llibre]

Yes, but you'd lose the capability to capture the error messages.
Response.redirect doesn't let you do that.

 

[jvcoach23]

so if you wnat to handle page not found links that are not aspx extensions,
like pdf files, then you need to use the customer error handling... cause
that won't go through the global... am i understanding that right.. is the
custom error the only option at that point... at least from a more web site
prospective..

thanks
shannon

 

[jvcoach23]

if i do the error message capturing before the server.transfer.. then i'd
be able to get the error message ok... that sound correct..

thanks
shannon

 

[Juan T. Llibre]

Yes. That's exactly what the sample I posted for you does.