From c4e1ab64fcae74caaf11093086853f407f0c3fbd Mon Sep 17 00:00:00 2001
From: Jimmy Everling <jimmy@jimmyk.se>
Date: Sun, 4 Aug 2024 22:21:39 +0200
Subject: [PATCH 1/3] Added reverse proxy configuration example for IIS with
 ARR & Url Rewrite

Signed-off-by: Jimmy Everling <jimmy@jimmyk.se>
---
 reverse-proxy.md | 57 ++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 57 insertions(+)

diff --git a/reverse-proxy.md b/reverse-proxy.md
index 9a4f80ab..517da7be 100644
--- a/reverse-proxy.md
+++ b/reverse-proxy.md
@@ -639,6 +639,63 @@ The examples below define the dynamic configuration in YAML files. If you rather
 
 </details>
 
+### IIS with ARR and URL Rewrite
+
+<details>
+
+<summary>click here to expand</summary>
+
+**Disclaimer:** It might be possible that the config below is not working 100% correctly, yet. Improvements to it are very welcome!
+
+#### Prerequisites
+1. **Windows Server** with IIS installed.
+2. [**Application Request Routing (ARR)**](https://www.iis.net/downloads/microsoft/application-request-routing) and [**URL Rewrite**](https://www.iis.net/downloads/microsoft/url-rewrite) modules installed.
+3. [**WebSocket Protocol**](https://learn.microsoft.com/en-us/iis/configuration/system.webserver/websocket) feature enabled.
+
+
+In the web.config example below, a Server farm named `nc-server-farm` has been created an is pointing to the Nextcloud server:
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<configuration>
+  <system.web>
+    <!-- Allow all urls -->
+    <httpRuntime requestValidationMode="2.0" requestPathInvalidCharacters="" />
+  </system.web>
+  <system.webServer>
+    <rewrite>
+      <rules>
+        <!-- Force https -->
+        <rule name="Https" stopProcessing="true">
+          <match url="(.*)" />
+          <conditions>
+            <add input="{HTTPS}" pattern="^OFF$" />
+          </conditions>
+          <action type="Redirect" url="https://{HTTP_HOST}/{REQUEST_URI}" appendQueryString="false" />
+        </rule>
+        <!-- Redirect to internal nextcloud server -->
+        <rule name="To nextcloud" stopProcessing="true">
+          <match url="(.*)" />
+          <conditions>
+            <add input="{HTTPS}" pattern="^ON$" />
+          </conditions>
+          <action type="Rewrite" url="http://nc-server-farm:11000/{UNENCODED_URL}" appendQueryString="false" />
+        </rule>
+      </rules>
+    </rewrite>
+    <security>
+      <!-- Increase upload limit to 2GiB -->
+      <requestFiltering allowDoubleEscaping="true">
+        <requestLimits maxAllowedContentLength="2147483648" />
+      </requestFiltering>
+    </security>
+  </system.webServer>
+</configuration>
+
+```
+
+</details>
+
 ### Others
 
 <details>

From 8bf7a4d57f28de38bbd684867fce8afc340439f3 Mon Sep 17 00:00:00 2001
From: Jimmy Everling <jimmy@jimmyk.se>
Date: Mon, 5 Aug 2024 18:29:20 +0200
Subject: [PATCH 2/3] Added link to "Adapting the sample web server
 configurations below"

Signed-off-by: Jimmy Everling <jimmy@jimmyk.se>
---
 reverse-proxy.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/reverse-proxy.md b/reverse-proxy.md
index 517da7be..db9d7629 100644
--- a/reverse-proxy.md
+++ b/reverse-proxy.md
@@ -693,6 +693,7 @@ In the web.config example below, a Server farm named `nc-server-farm` has been c
 </configuration>
 
 ```
+⚠️ **Please note:** Look into [this](#adapting-the-sample-web-server-configurations-below) to adapt the above example configuration.
 
 </details>
 

From eb3a133a0c9ab6ab48d886efc80b6841f40b2dab Mon Sep 17 00:00:00 2001
From: Jimmy Everling <jimmy@jimmyk.se>
Date: Tue, 6 Aug 2024 19:45:21 +0200
Subject: [PATCH 3/3] Rewrote the instructions to make them clearer.

Signed-off-by: Jimmy Everling <jimmy@jimmyk.se>
---
 reverse-proxy.md | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/reverse-proxy.md b/reverse-proxy.md
index db9d7629..1ea7b179 100644
--- a/reverse-proxy.md
+++ b/reverse-proxy.md
@@ -647,14 +647,24 @@ The examples below define the dynamic configuration in YAML files. If you rather
 
 **Disclaimer:** It might be possible that the config below is not working 100% correctly, yet. Improvements to it are very welcome!
 
+**Please note:** Using IIS as a reverse proxy comes with some limitations:
+- A maximum upload size of 4GiB, in the example configuration below the limit is set to 2GiB.
+
+
 #### Prerequisites
 1. **Windows Server** with IIS installed.
 2. [**Application Request Routing (ARR)**](https://www.iis.net/downloads/microsoft/application-request-routing) and [**URL Rewrite**](https://www.iis.net/downloads/microsoft/url-rewrite) modules installed.
 3. [**WebSocket Protocol**](https://learn.microsoft.com/en-us/iis/configuration/system.webserver/websocket) feature enabled.
 
+For information on how to set up IIS as a reverse proxy please refer to [this](https://learn.microsoft.com/en-us/iis/extensions/url-rewrite-module/reverse-proxy-with-url-rewrite-v2-and-application-request-routing).
+There are also information on how to use the IIS Manager [here](https://learn.microsoft.com/en-us/iis/).
 
-In the web.config example below, a Server farm named `nc-server-farm` has been created an is pointing to the Nextcloud server:
+The following configuration example assumes the following:
+* A site has been created that is configured with HTTPS support and the desired host name.
+* A server farm named `nc-server-farm` has been created and is pointing to the Nextcloud server.
+* No global Rewrite Rules has been created for the `nc-server-farm` server farm.
 
+Add the following `web.config` file to the root of the site you created as the reverse proxy.
 ```xml
 <?xml version="1.0" encoding="UTF-8"?>
 <configuration>