Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#60842 - [transmission-remote-gtk] cannot connect behind some proxy servers

Attached to Project: Community Packages
Opened by Bert Peters (bertptrs) - Saturday, 17 November 2018, 19:06 GMT
Last edited by Bruno Pagani (ArchangeGabriel) - Monday, 10 December 2018, 19:09 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Bruno Pagani (ArchangeGabriel)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



Starting transmission 1.4.0, the web interface has some CSRF protection header that needs to be echo'd back to the server. However, the remote gtk client (possibly the cli client too, haven't tested it) does a case-sensitive match on the header. At least in my set up (transmission behind nginx) the header comes out as lowercase, while the check is for a mixed case version, and so the connection fails with HTTP 409/Conflict.

Upstream has accepted a patch fixing this, but haven't made a release yet. The relevant patch is attached.

Additional info:
* transmission-remote-gtk 1.4.0-1 from the repository
* connecting to transmission-cli 2.94-1 (from arch linux arm, but that is not relevant to the actual bug, since it is the client that is wrong)

Steps to reproduce:
* have transmission daemon running
* behind a proxy that "normalizes" or otherwise changes headers
* try to connect using the gtk client
This task depends upon

Closed by  Bruno Pagani (ArchangeGabriel)
Monday, 10 December 2018, 19:09 GMT
Reason for closing:  Fixed
Additional comments about closing:  Actually, I faced the same issue and I’m the one who reported this upstream. So I’ve build a version with the fix, tested it and later pushed to the repo as transmission-remote-gtk 1.4.0-2. ;)

Strangely another user of my server had no issues until updating their ArchLinux laptop too…