Hello,
I am running Transmission-daemon via the Transmission-cli package under Arch Linux ARM on a Raspberry Pi 3.
I am informed by one specific tracker that my client does not send a user agent, which is a tracker requirement to identify clients, when announcing.
I am not sure whether this is Arch-specific, so I am wondering if anyone could confirm whether non-Arch Transmission-daemons send an empty user agent for v3.0.
According to https://archlinuxarm.org/packages/armv7 ... ission-cli, I am not seeing anything specific that would change the default user agent when building.
I've also tried to add a:
"user-agent": "Transmission/3.00 (bb6b5a062e)"
line to my *settings.json*, unfortunately, I am still getting the issue.
Any help is greatly appreciated.
Erion
[3.00, Solved] Empty user agent is send when announcing
[3.00, Solved] Empty user agent is send when announcing
Last edited by erion on Wed Jul 08, 2020 10:41 am, edited 1 time in total.
Re: [3.00] Empty user agent is send when announcing
To add to this, it seems that Curl 7.71 and above does not send the user agent reliably, at least on Arch Linux. I am not sure whether this is a packaging issue.
Building v2.94 of Transmission-cli resulted in the same issue, but the moment I built and downgraded Curl, the issue was gone.
This is hopefully helpful information for anyone having the same issue.
Building v2.94 of Transmission-cli resulted in the same issue, but the moment I built and downgraded Curl, the issue was gone.
This is hopefully helpful information for anyone having the same issue.