Iis – Rewrite IIS served subdomain with content from other server/port

iisiis-6reverse-proxyrewrite

Our main web server is using IIS 6 and it obviously catches all port 80 traffic and we have another app served on a non-standard port (8443) that is hosted using Apache.

For example:

http://www.mydomain.com -> IIS6
http://subdomain.mydomain.com:8443 -> Apache App
http://subdomain.mydomain.com -> IIS6

I would like to be able to access the Apache app without using port 8443. That is, IIS should rewrite/proxy content from the Apache app on the different port. Note: I do not want to redirect the user.

http://subdomain.mydomain.com -> IIS <-> http://subdomain.mydomain.com:8443 -> Apache App

Is this possible? What tools should I use?

Best Answer

This is called Reverse proxy.

And yes, this is possible for most web applications.

As to the tools, I think your best bet is to try this with the great IIRF - Ionic's Isapi Rewrite Filter - IIRF works great on IIS6, and it's fast and free.

Though I only had to use Apache's mod_proxy to set up a reverse proxy (but IIRF for rewriting urls on other sites), IIRF should be up to the task.

From the FAQ:

Can IIRF act as a transparent proxy (like Apache's mod_proxy)?

Yes. ProxyPass, ProxyPassReverse, and ProxyPreserveHost are supported.

The documentation of IIRF contains actually very concise information about setting up (reverse) proxies, as well as some guidance on what to look out for:

Related Solutions

Cannot 301 redirect with IIS URL Rewrite Module

The patterns are relative to the root of the site, not including the domain name, so in this case, the pattern should be:

^test\.html

This will match http://example.com/test.html and then apply the rules you have set for it.

IIS URL Rewrite HTTP to HTTPS with Port

Even though the question was answered awhile ago, this is the rule that I used.

<rule name="Redirect to HTTP on different port" enabled="true" stopProcessing="true">
      <match url="(.*)"/>
      <conditions>
        <add input="{HTTPS}" pattern="ON"/>
      </conditions>
      <!-- Cannot Use {HTTP_HOST} as it contains both the {SERVER_NAME}{SERVER_PORT} -->
      <action type="Redirect" url="http://{SERVER_NAME}:1000{HTTP_URL}" redirectType="Found" appendQueryString="false"/>
    </rule>

Best Answer

Related Solutions

Cannot 301 redirect with IIS URL Rewrite Module

IIS URL Rewrite HTTP to HTTPS with Port

Related Topic