Sorry for asking some basic question(s). After studying
URLrewriter and working with it for a while, I may come in with a different view at Iconics Isapi Rewriter then I actually should have. Maybe I need to get some terminology straight, but I am sure there are a few folks on here that will be able to
Let me start of with a 10,000ft overview: I have a MS Windows 2003 Server ISS6 machine, which is the primary target for inbound WAN connections. So all port 80 communication goes to the MS Win 2003 box with IIS6. Inside the LAN I got another machine with
Apache2 running. I would like to simply route traffic from IIS6 to Apache - not redirect, but simply rewrite some URL headers, since redirect would require me to publish a different URL and port number.
In other words, I may have a site http://www.mydomain.com and a subpage
http://subpage.mydomain.com - the first would go to IIS and be handled on Windows Server, the second should be reverse proxied ("reverse proxy") from
Windows to Apache2. I found some articles in this forum from 4/2008 time frame that state that reverse proxy is not available with Ionics. However, the Operator's Guide clearly spells out "reverse proxy"
for the "ProxyPass" function (maybe a feature added in a later version).
So, while I was using "RewriteRule" with "URLrewriter", I am wondering if that function does something other than reverse proxy for Ionics. Do I need to use ProxyPass instead, or will I have to use "RewriteRule" with Ionics
as well for being able to have certain pages served from the Apache2 server rather than IIS6?
You may be asking of why I am not using URLrewriter any longer? - Well, that answer unfortunately is pretty simple as URLrewriter is
not able to handle (basic) authentication correctly using reverse proxy. I know digest authentication would never work, so I tried my luck with basic authentication.
Now I want to find out if "Ionics Isapi Rewrite Filter" will be able to handle that any better.
One of the basic setup questions that remains is also of how to configure and setup IIS6 correctly so that Ionics will e.g. handle requests for
http://subpage.mydomain.com but not
http://www.mydomain.com? I have created a virtual site called subpage.mydomain.com and pointed that to a specific folder beneath wwwroot. I have placed a special iirf.ini file in that folder and made sure that the global iirf.ini will include it. However,
when I enter subpage.mydomain.com in the web browser on the IIS6 machine, I get a 403 error response.
Setup so far:
# IIRF.INI file
# IIRF.INI file
ProxyPass .*.com(/?(subpage)?/?)?/?(.*) http://apache2/subpage/$3 [P]
BTW: The page http://apache2/subpage/ does pull up nicely within IE7 on the Windows 2003 Server box when entered directly. Basic authentication is working as well when used this way.
So, I guess the two main questions are:
1) Will I have to use "RewriteRule" or "ProxyPass" - or will none of them work for what I need?
2) What configuration changes are necessary for IIS6 to initiate Ionics rather than trying to find the page locally? Will a Web.config be required and if so, what content will be necessary?
Thank you all for your help in advance - I hope it will help somebody else as well!