Configuration of Forwarding Rules with URL Rewrite

This section describes how to create redirection rules with URL Rewrite. Generally, in each node in IIS which could receive requests, the user will find the possibility of URL Rewrite forwarding rules.

Step 1: Definition of a forwarding rule on the WebServer

In the following example, the forwarding rule is set up globally on the IIS web server. This means that this forwarding rule is always applied as soon as the prerequisite of the rule (e.g. rule pattern or criteria) is fulfilled.


The function of the forwarding rules can be found at the application view in the section IIS.


Opening the forwarding rules in IIS

Opening the forwarding rules in IIS


After opening the URL Rewrite Module all rules are listed which are already configured. Generally, inactive rules are displayed in gray (no influence on requests) and active rules are displayed in black color. Via button Add New Rule you can create a new rule for redirection, modification, HTTP header change and many other application possibilities.


Adding or editing a forwarding rule with URL Rewrite

Adding or editing a forwarding rule with URL Rewrite


In the next dialog, predefined rules can be selected from templates (e.g. request blocking, URL formatting rules, etc.). In the case of the forwarding rule, an empty rule is created, which is then adjusted according to the forwarding page. In this example, an incoming rule is sent to the server.


Depending on the communication direction, either an incoming rule or an outgoing rule must be defined.


Creating rules with URL Rewrite

Creating rules with URL Rewrite


When creating an incoming rule, there are 4 different areas which can be configured. The following table shortly describes the different ranges.



Short description


The Pattern section is used to specify the pattern of URLs to which the following rules will be applied. It is possible to define rules using regular expression or wildcard patterns.


This optional parameter specifies logical operations if a URL matches the pattern. The conditions can be used to query different values of HTTP headers or server variables or to check whether the URL points to a corresponding file or directory on the physical file system.

Server Variables

Server variables enable the enrichment of additional information about the submitted HTTP requests.


The action is used to define the redirecting URL or HTTP code for those URLs that match the rule pattern.


In the example of the rule for a forwarding page all requests with the pattern WebOffice* (application name) are retrieved and redirected to a corresponding URL.


Selected pattern
Regular Expression with wildcard WebOffice*

Server variable
RESPONSE_Pragma - no-cache

Redirect type Redirect
http://<server-name>/<directory/index.html (see chapter Setup a Maintenance Page in IIS)


Creating an IIS redirection rule with URL rewrite

Creating an IIS redirection rule with URL rewrite


For the server variable, the value is set at the parameter RESPONSE_Pragma to no-cache so that the request is not stored in the browser cache. This has the advantage that when the forwarding rule is disabled, the user does not have to clear the browser cache.

Server variable of the header to avoid caching

Server variable of the header to avoid caching


The rule must then be adopted in the right area of the rule. This makes it possible to complete the set up of a forwarding rule with URL hosts in the IIS.



For more information on how to install the necessary modules to set up a redirect page, please refer to chapter Installation of IIS Extensions (IIS ARR, URL Rewrite).

For more information about the configuration of the IIS ARR module, refer to chapter Configuration or Setup of IIS ARR.

For more information on how to set up a forwarding page, refer to chapter Setup a Maintance Page in IIS.

For more information on how to activate or deactivate the rules in IIS, please refer to chapter Activation or Deactivation of the Forwarding Rule in IIS.