if i set up a mapping of .asp file to aspnet_isapi, how do i handle the many
cases where asp.dll needs to handle a request? i only want to rewrite
certain .asp requests that match a signature i'm looking for, e.g.,
MyPage.asp?mode=5 would be mapped to MyNewPage.aspx, whereas
MyPage.asp?mode=4 should be processed by asp.dll.
Here's what happened: someone wrote a GIGANTIC asp page that handles all
sorts of stuff based on a "mode." It posts to itself and takes different
paths based on which mode its in, i.e., update, display, etc. To add to the
devastation, the code in question runs inside of an iframe, so I can't
Server.Transfer or Redirect in the asp code.
thanks
"gerry" wrote:
you can map anything and everything to aspnet_isapi.dll in IIS.
we commonly map .htm .html and .asp to aspnet_isapi.dll and rewrite the url
when the request hits our web app.
"T" <T@discussions.microsoft.com> wrote in message
news:E3**********************************@microsof t.com... Hi group,
I'm trying to create a temporary replacement scheme for a particular url
that gets generated all over an existing app. It would be very difficult
to find every spot where the url gets created. So I'm thinking of doing a
url rewrite solution where i look for the url signature at the application (or
higher?) level. The twist is that the original url is classic asp. So
how do I grab this asp url from a .net httpmodule (or other thing) and
redirect the request to an aspx page? Of course you can't map .asp files to
aspnet_isapi.dll in IIS. Can this be done?
Thanks for any ideas...