squidy/qBittorrent
1
0
Fork 0
mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-01-09 09:02:31 -06:00
Code Issues Packages Projects Releases Wiki Activity

update proxy configuration

Francisco Pombal
2020-01-25 01:02:47 +00:00
parent b0eaab7f57
commit 62df99e855
1 changed files with 14 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
Linux-WebUI-HTTPS-with-Let's-Encrypt-certificates-and-NGINX-SSL-reverse-proxy.md

@@ -111,18 +111,22 @@ server {
location /qbt/ { location /qbt/ {
# you can use any other port other than 30000 as long as it is available on your system # you can use any other port other than 30000 as long as it is available on your system
proxy_pass http://127.0.0.1:30000/; proxy_pass http://127.0.0.1:30000/;
proxy_set_header X-Forwarded-Host $server_name:$server_port;
proxy_hide_header Referer;
proxy_hide_header Origin;
proxy_set_header Referer '';
proxy_set_header Origin '';
# if you use the "enable host header validation" setting with 127.0.0.1 in the "server domains" text box proxy_http_version 1.1;
# don't forget to change the port number to the one you are actually using. proxy_set_header X-Forwarded-Host $http_host;
# proxy_set_header Host 127.0.0.1:30000;
# not needed since 4.1.0 # The following directives effectively nullify Cross-site request forgery (CSRF)
# add_header X-Frame-Options "SAMEORIGIN"; # protection mechanism in qBittorrent, only use them when you encountered connection problems.
# You should consider disable "Enable Cross-site request forgery (CSRF) protection"
# setting in qBittorrent instead of using these directives to tamper the headers.
# The setting is located under "Options -> WebUI tab" in qBittorrent since v4.1.2.
#proxy_hide_header Referer;
#proxy_hide_header Origin;
#proxy_set_header Referer '';
#proxy_set_header Origin '';
# Not needed since qBittorrent v4.1.0
#add_header X-Frame-Options "SAMEORIGIN";
# in a future version of qBittorrent (probably 4.2.2), # in a future version of qBittorrent (probably 4.2.2),
# it will be possible to set the "Secure" flag for the session cookie, # it will be possible to set the "Secure" flag for the session cookie,