> When a page is requested and not found (common error 404), we can get
> control back at IIS level and, for instance, trough an ASP page, provide
the
> user with some hints to redirect his request.
using the "Custom Error" concept and make error points to an .ASP page (for
instance)
> Unfortunately, the custom error page (ASP) is not given any mean for
> retrieving variables of the request if those were sent through GET (or
POST)
> method. QUERY_STRING variable contains the path to the page asked without
> "?variable=value" information, QueryString and Form collections are empty.
> The QUERY_STRING server variable is filled with "404;<original URL without
> parameters>".
Actually, it works EXCEPT when the original page that user was trying to
access is an .asp page, if he tries with
<a style='text-decoration: underline;' href="http://myserver/MyDummyPage.htm?MyVar=MyValue" target="_blank">http://myserver/MyDummyPage.htm?MyVar=MyValue</a> it works... if he tries with
<a style='text-decoration: underline;' href="http://myserver/MyDummyASPPage.asp?MyVar=MyValue" target="_blank">http://myserver/MyDummyASPPage.asp?MyVar=MyValue</a> it FAILS!
> Do anyone have idea on how to get access to those parameters transferred
by
> the browser to the server in the original request?<!-- ~MESSAGE_AFTER~ -->
FAQ
Profile
Private Messages
Log in
