Pregunta

I am trying to figure out if its possible to do a Reverse Proxy in IIS that actually hit a different web server end point. I have used it to traverse Ports on the same machine, but never to a different machine. The purpose of this is that I am writing a Javascript application that needs to connect to data on a different server and I am getting Same Origin errors.

Note: Unfortunately, changing the remote server and service to accept JSONP or CORS is not an option.

Here is the config for Port jumping using IIS Reverse Proxy

<system.webServer>      
        <rewrite>
            <rules>
                <rule name="Reverse Proxy to Different Port" stopProcessing="true">
                    <match url="^name/(.*)" />
                    <action type="Rewrite" url="http://localhost:5984/{R:1}" />
                </rule>
            </rules>
        </rewrite>
</system.webServer>
¿Fue útil?

Solución

To make this work, you need to have Application Request Routing (AAR) installed on the IIS server you want to act like the reverse proxy. After that, then add the following into the web.config:

<system.webServer>      
    <rewrite>
        <rules>
            <rule name="Reverse Proxy to Different Port" stopProcessing="true">
                <match url="^name/(.*)" />
                <action type="Rewrite" url="http://[hostname here]:[port number here]/{R:1}" />
            </rule>
        </rules>
    </rewrite>
</system.webServer>

This will redirect any request where the path starts with name/ to the other server. So if you're seeking /foo/bar on the remote server, you would need Javascript to request /name/foo/bar to the IIS server that has the reverse proxy configured.

Licenciado bajo: CC-BY-SA con atribución
No afiliado a StackOverflow
scroll top