From 26630b10b9031c37ecd67ce3f1cc465690baa101 Mon Sep 17 00:00:00 2001 From: Francisco Pombal Date: Sun, 22 Dec 2019 19:13:38 +0000 Subject: [PATCH] update nginx config --- ...Encrypt-certificates-and-NGINX-SSL-reverse-proxy.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/Linux-WebUI-HTTPS-with-Let's-Encrypt-certificates-and-NGINX-SSL-reverse-proxy.md b/Linux-WebUI-HTTPS-with-Let's-Encrypt-certificates-and-NGINX-SSL-reverse-proxy.md index dc35031..25fe98e 100644 --- a/Linux-WebUI-HTTPS-with-Let's-Encrypt-certificates-and-NGINX-SSL-reverse-proxy.md +++ b/Linux-WebUI-HTTPS-with-Let's-Encrypt-certificates-and-NGINX-SSL-reverse-proxy.md @@ -73,7 +73,7 @@ cd /etc/nginx/sites-enabled/ sudo ln -s /etc/nginx/sites-available/yoursite yoursite ``` 5. Open the file with your favourite text editor and paste something like the following (read the comments, which start with `#` to know what you have to change): -```shell +```nginx # change "yourdomain.com" and similar to your actual domain server { listen 80; @@ -115,7 +115,13 @@ server { proxy_hide_header Origin; proxy_set_header Referer ''; proxy_set_header Origin ''; - add_header X-Frame-Options "SAMEORIGIN"; # see note + + # in a future version of qBittorrent (probably 4.2.2), + # it will be possible to set the "Secure" flag for the session cookie, + # but only if using qBittorrent's HTTPS functionality. + # For this use case, where qBittorrent itself is using HTTP, + # set this flag by overriding it in the proxy configuration it itself: + # proxy_cookie_path / "/; Secure"; } # OPTIONAL: serve static HTML files at the root of the domain, like a simple homepage