Jul 29, 2009 at 11:50 AM
Edited Jul 29, 2009 at 1:52 PM
Turn off wouldn't make any sense, because the page that is redirected to (by the way there are many more website aliases in this IIS configured it just works as central point to forward the aliases to serveral Application Servers, that play out JSP sites)
can't be played out from IIS.
Heres how it works:
User requests an Alias -> IIS looks for the alias and redirects to the responsible Application Server -> Server parses JSP and sends the displayable page
So the requested page does not lie on an IIS webroot, it lies on another (physical) Server.
On IIS 6 it works like that:
User requests alias -> IIS (with ISAPI Filter activated) looks in Header if there is a known Mobile Header -> If yes it redirects to the mobil page / if no, the typicall redirect of this alias is done.
On IIS 5 it does similar, but:
User requests alias -> If alias shows to a loca folder it does the same as on IIS 6 / If the alias shows on a redirect URL the ISAPI Filter doesn't recognize the request and the alias is forwardet to the non-mobile-page in every case.
IIS5 seems to need a local directory where it shows to, to get the ISAPI Plugin used.
I read, that IIS6 uses a other Apllication Process Model, then IIS5.
Turn off hard redirect is not possible, because IIS wouldn't play out the JSP pages anymore.
I only wanted to know if this used to work like that under IIS 5 (that it only works on directory forwarding and not for hard redirects). I thought the ISAPI filter would monitor the alias itself an not the method how the redirect is done.