Example configuration IIS

Example configuration IIS

Install Application Request Routing (ARR for short)

The first step is to install the add-on module for Application Request Routing for IIS. With Windows Server 2012 R2 or later versions of Windows Server 2016 and 2018, you can use the Microsoft Web Platform Installer 5.1 (WebPI) to download and install the URL Rewrite Module. Just search for ‘URL Rewrite’ in the search options and click ‘Add’. You can also download the extension from IIS.net - https://www.iis.net/downloads/microsoft/application-request-routing.


Once the module is installed in IIS, you will see a new Icon in the IIS Administration Console, called URL Rewrite - you may note that Url Rewrite is also an add-on that can be installed separately, but that ARR uses functionality provided by Url Rewrite to allow the server to act as a reverse proxy. This icon is present at the level or each site and web-application you have in the server, and will allow you to configure re-write rules that will apply from that level downwards.

Setup a Reverse Proxy rule using the Wizard.

Open the IIS Manager Console and click on the Default Web Site from the tree view on the left. Select the URL Rewrite Icon from the middle pane, and then double click it to load the URL Rewrite interface.


Chose the ‘Add Rule’ action from the right pane of the management console, and the select the ‘Reverse Proxy Rule’ from thNow we can proceed to fill in the routing information based on the diagram above in the Wizard window that is provided to us.

While still in the same configuration window, we also need to provide information to take care of the responses that will be emitted by the backend server and will transit the IIS server on their way back to the requesting browser. These responses may have absolute hyperlinks inside and other information which contains the hostname of the backend server. If these are sent to the browser as is, the end user will not be able to access the resources these links point to simply because the browser does not know where http://localhost:7070 is located and how it can be reached. We need to convert these into the hostname of the reverse proxy server, and have them look like: https://mypublicserver.com/ . For this reason, we will check the ‘Rewrite the domain names of the links in HTTP responses’ checkbox in the Outbound Rules section. Fill in 
  1. From: localhost:7070
  2. To: your domainname. For example: https://salureconnect.customer.com

The basic setup for the reverse proxy is now complete, with IIS able to capture incoming traffic and forward it to the backend server, and inspect responses from the backend server and rewrite URL links inside the responses to match the host headers that IIS uses to publish the site.


    • Related Articles

    • Requirements and installation

      In order to run the agent correctly, the following setup is required. Hard- en software requirements Windows Server 2012 64 bit or 2016 64 bit with 8 GB Ram, minimal of 2 CPU cores with 2.40 GhZ, 150 GB hard drive; Connection to the internet ...

    • Set File Definition

      Users can upload files into SalureConnect. These files can then be used in dashboards or forwarded to external systems. This article describes how the File Upload functionality is set up. Add A user cannot upload files until a definition exists. A ...

    • Security

      SalureConnect'sagent is a web server without a front-end. This means that security issues suchas CORS, XSS, CSRF etc. are not applicable. The main security issues are authentication,encryption and rate-limiting. Authenticatie A request to the agent ...

    • Setup Organigram

      The organizational chart determines what users see in the dashboards. This article describes how to set up the organizational chart and how to link users to it. Loading source systems In most organizations, multiple software systems are used for ...

    • User management

      This article describes how to add users and how to assign them appropriate permissions. Add a user Navigate to Settings > Authorization > Users; Click on "Create" at the top right of the table; In the screen that follows, enter a name and email ...