LAB-linuxserver/reverse-proxy-confs
1
0
Fork 0
mirror of https://github.com/linuxserver/reverse-proxy-confs.git synced 2026-02-20 04:59:12 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #155 from n-i-x/master

Browse Source 
Add a note about HTTP/2 and Transmission Chrome Extensions
This commit is contained in:
Eric Nemchik 2020-04-28 13:36:05 -05:00 committed by GitHub
commit fb47872e88
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 22 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
transmission.subdomain.conf.sample
View File

@ -1,4 +1,14 @@
# make sure that your dns has a cname set for transmission
# Make sure that DNS has a cname set for transmission
#
# Some Transmission Chrome extensions cannot handle HTTP/2 proxies as they
# rely on the HTTP Status Text to determine if they should add the
# X-Transmission-Session-Id header or not. HTTP/2 does not return this text
# so jQuery responses are empty. This causes RPCs to fail.
#
# If your extension is affected, you can remove http2 from the default server
# in /config/nginx/site-confs/default or listen on a different port that has
# no http2 servers defined. Better yet, submit a bug report with the
# extension developer to fix their extensions to support HTTP/2.
server {
listen 443 ssl;

12
transmission.subfolder.conf.sample
View File

@ -1,4 +1,14 @@
# transmission does not require a base url setting
# Transmission does not require a base url setting
#
# Some Transmission Chrome extensions cannot handle HTTP/2 proxies as they
# rely on the HTTP Status Text to determine if they should add the
# X-Transmission-Session-Id header or not. HTTP/2 does not return this text
# so jQuery responses are empty. This causes RPCs to fail.
#
# If your extension is affected, you can remove http2 from the default server
# in /config/nginx/site-confs/default or listen on a different port that has
# no http2 servers defined. Better yet, submit a bug report with the
# extension developer to fix their extensions to support HTTP/2.
location ^~ /transmission {
# enable the next two lines for http auth