# IIS (Microsoft Windows Server) Configuration Guide
### **Introduction**
This guide explains configuring **Microsoft IIS (Internet Information Services)** as a reverse proxy using the **Application Request Routing (ARR)** module. IIS with ARR allows you to forward incoming HTTP requests to one or more backend servers, providing benefits like **load balancing**, **centralized traffic management**, and **security filtering**.
***
### **Prerequisites**
* Microsoft Windows Server with **IIS** installed.
* IIS URL Rewrite
Download and install the [URL Rewrite](https://www.iis.net/downloads/microsoft/url-rewrite) extension.
URL Rewrite must be installed prior to ARR, as ARR depends on URL Rewrite.
* IIS Application Request Routing (ARR)
Download and install the [Application Request Routing](https://www.iis.net/downloads/microsoft/application-request-routing) extension.
After installation, you should see the **Application Request Routine Cache** and **URL Rewrite** features in the IIS Manager.
***
### **Configuration Steps**
#### **1. Activate Proxy**
-Open the IIS manager, select the server in the **Connections** pane, and then double-click **Application Request Routing Cache** to open the feature.
In the **Actions** pane, click **Server Proxy Settings**.
On the **Application Request Routing** page, select **Enable Proxy**; and then in the **Actions** pane, click **Apply**. This enables ARR as a proxy at the server level.
#### **2. Create a URL Rewrite Rule**
To route incoming requests to the backend server:
1. In **IIS Manager**, select the **site** you want to configure.
2. Double-click **"URL Rewrite"**.\
3. In the Actions pane, click **"Add Rules…"**.
4. Under **Inbound Rules**, choose **"Blank Rule"** and click **OK**.\
**Rule Configuration**
Click **OK** in the Actions pane to save the rule.
***
### **Conclusion**
You’ve successfully configured IIS with ARR as a reverse proxy. This setup allows you to forward requests transparently while retaining the ability to apply additional logic via rewrite rules or filters.
{% hint style="danger" %}
After enabling Cookie lifetime extender, the DCP will give a proxy code that is expected to be setup on `https://domain.*/hash` however, if it is set up on `https://www.domain.*/hash` it will cause a CORS Error on the Cookie Lifetime Extender Requests.
For more details on WWW configuration follow this [guide](https://docs.jentis.com/key-features/cookie-lifetime-extender/configure-your-tracking#www-configuration-guide-optional).
{% endhint %}
***
If you have any questions or feedback, please open a request on our [Helpdesk](https://jentis.atlassian.net/servicedesk/customer/portal/1/group/1/create/220).
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.jentis.com/key-features/cookie-lifetime-extender/cookie-lifetime-extender-webserver-cdn-configurations/iis-microsoft-windows-server-configuration-guide.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.