IIS 7 and Above
Application Request Routing (ARR)
Using IIS on a public facing website to present an internal web appli...
Last post Jul 06, 2016 02:31 PM by gregbooth2
Jul 05, 2016 10:12 AM|gregbooth2|LINK
We have a new web based system that uses an Apache web server that talks to other servers and databases. The apache box was due to go in our DMZ and be public facing but due to security concerns (cannot go into the details) about the application architecture
we are going to
a) put an addtitional server running IIS in our dmz.
b) This IIS server will redirect (https) traffic though the firewall to the apache box.
i.e. the original application is available at
The public will go to https://subdomain.mycompany.com - which maps to the server running IIS - this needs to pass traffic back and forth to https://apache.landomain.local/appname .
ie from the publics point of view they are just seeing the web application on the apache server.
Should we be using AAR for this ?
Would anyone be so kind to point me to the best documentation re how to configure IIS/AAR.
The IIS server will be running Windows 2012 R2.
Jul 05, 2016 11:45 PM|terridonahue|LINK
blog post should provide all the information you need to configure IIS as a reverse proxy.
Jul 06, 2016 02:16 AM|Jean Sun|LINK
To achieve this, you need to configure your IIS server as reverse proxy.
To configure IIS Server as reverse proxy, you need to use IIS URL Rewrite Module and ARR.
You can take the following link as reference:
Jul 06, 2016 02:31 PM|gregbooth2|LINK