From 985052ef9740d14ce6f7ea605582798737e12492 Mon Sep 17 00:00:00 2001 From: kimboslice99 <94807745+kimboslice99@users.noreply.github.com> Date: Mon, 20 Jan 2025 00:32:53 -0500 Subject: [PATCH] Update IIS-ARR-Reverse-Proxy.md (#21) Adding server port breaks csrf. Server variables are with underscores. --- IIS-ARR-Reverse-Proxy.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/IIS-ARR-Reverse-Proxy.md b/IIS-ARR-Reverse-Proxy.md index 9145847..c3d2790 100644 --- a/IIS-ARR-Reverse-Proxy.md +++ b/IIS-ARR-Reverse-Proxy.md @@ -6,8 +6,8 @@ For users that run qBittorrent via Microsoft IIS as a reverse proxy some extra h 4. Create a new site that will handle the reverse proxy requests 5. Select the site and then open **URL Rewrite** 6. On the right hand side, open **View Server Variables** -7. Click **Add** and in the box that appears enter `HTTP_X-Forwarded-Host` -8. Repeat this for `HTTP_X-Forwarded-For` and `RESPONSE_Set_Cookie` +7. Click **Add** and in the box that appears enter `HTTP_X_Forwarded_Host` +8. Repeat this for `HTTP_X_Forwarded_For` and `RESPONSE_Set_Cookie` 9. Return to the rules page 10. Open **Add Rules** and select **Reverse Proxy** 11. Enter the server IP:Port without `http://` (for example `127.0.0.1:8080`), then click **OK** @@ -16,8 +16,8 @@ For users that run qBittorrent via Microsoft IIS as a reverse proxy some extra h | Server variable name | Value | | --------------------- | ------------------------- | - | HTTP_X-Forwarded-Host | {HTTP_HOST}:{SERVER_PORT} | - | HTTP_X-Forwarded-For | {REMOTE_ADDR} | + | HTTP_X_Forwarded_Host | {HTTP_HOST} | + | HTTP_X_Forwarded_For | {REMOTE_ADDR} | 14. Apply and return to the rules page 15. Open **Add Rules** and select **Blank rule** under **Outbound rules** @@ -35,8 +35,8 @@ The result should look similar to this in your web.config (Note: you must use th - - + + @@ -48,8 +48,6 @@ The result should look similar to this in your web.config (Note: you must use th ``` -Additionally you must untick **Enable Cross-Site Request Forgery (CSRF) protection** in qBittorrent's Web UI options for the reverse proxy to work. - You can use HTTPS to access the URL via IIS and it will use HTTP to communicate with qBittorrent. There is no need for HTTPS on localhost. Note: If you find yourself seeing `WebAPI login failure. Reason: IP has been banned, IP: 127.0.0.1` and needing to restart qBittorrent, you may want to set the ban after failure count to `0` which will disable it.