Text of github.com › curl › curl › issues › 6312 as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Libcurl does not seem to send user agent reliably · Issue #6312 · curl/curl · GitHub

Skip to content You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert Libcurl does not seem to send user agent reliably #6312 New issue Copy link New issue Copy link Closed Closed Libcurl does not seem to send user agent reliably #6312 Copy link Labels HTTP libcurl API Description Flameborn opened on Dec 12, 2020 Issue body actions Transmission does not always send a user agent string when announcing to a torrent tracker.

Even when specified in its config file, the sent user agent string is empty. This is after upgrading to Curl (libcurl) 7.71.0 and above, using Transmission 2.94 and 3.0. Older Curl versions work as expected. See a forum thread here: https://forum.transmissionbt.com/viewtopic.php?f=2&t=20449&sid=5ab5f6c305ead5a64dbd72b0608cf729 I expected the following User agent sent when announcing. curl/libcurl version Curl 7.71.0 and above. operating system Arch Linux ARM (Linux idris 5.4.81-1-ARCH #1 SMP PREEMPT Mon Dec 7 20:38:46 UTC 2020 armv7l GNU/Linux) Reacted by Paolo Rodríguez, Stefan Karpinski and Roberto Malatesta Activity Next bagder added HTTP libcurl API on Dec 12, 2020 bagder commented on Dec 12, 2020 bagder on Dec 12, 2020 Member More actions Please tell us how to reproduce this.

And if any of the details in that forum thread is important for the issue, I would appreciate if you would include them in the issue here. bagder changed the title [-] Libcurl does not seem to send user agent reliably when used via Transmission [/-] [+] Libcurl does not seem to send user agent reliably [/+] on Dec 12, 2020 Flameborn commented on Dec 12, 2020 Flameborn on Dec 12, 2020 Author More actions I am unfortunately unable to specify exact steps to reproduce, as the tracker specifics are not known to me.

As a result,I can only assume that this is a common issue with any tracker, possibly with HTTPS enabled. I am aware that this makes debugging and possibly fixing the issue a lot harder than it should be. In general: Install the transmission-cli package, along with core/curl (currently 7.74.0). Set up a torrent tracker, such as https://github.com/skipperbent/easy-torrent-tracker . (Requires a web server, PHP and possibly a certificate for HTTPS).

Use transmission-create to create a torrent file, specifying the locally installed tracker. Start transmission via systemctl . Add the previously created torrent file via transmission-remote -a torrent-file-name.torrent bagder commented on Dec 12, 2020 bagder on Dec 12, 2020 Member More actions I can only assume that this is a common issue with any tracker, That seems like a very far-going assumption that I can't see any evidence for.

We need a recipe for this issue in order to conclude that this is in fact a libcurl problem and not just a side effect of something in the application code. libcurl is after all used by a large number of applications and we've had no others report an issue like this during the half year 7.71.0 has been out. The fact that no user-agent appears when you run the application is not a sure sign of a libcurl issue... bagder added needs-info on Dec 12, 2020 Flameborn commented on Dec 12, 2020 Flameborn on Dec 12, 2020 Author More actions That seems like a very far-going assumption that I can't see any evidence for.

You are right, it is not guaranteed, but the fact that a Curl upgrade specifically causes this issue makes it likely that it was indeed a change in libcurl in 7.71.0. Transmission 2.94 was released on the 1st of May, 2018. This release and the subsequent 3.0 version (released on the 22nd of May 2020) work with Arch Linux's core/curl 7.70.0 and do not have issues when announcing. Supposing that there were some API changes for lib curl in 7.71.0 and above, and Transmission is not using the lib curl API as expected, so the user agent is not set properly and it is indeed an application side effect as suggested, I believe that this is something that should be handled as it might break backward compatibility. bagder commented on Dec 12, 2020 bagder on Dec 12, 2020 Member More actions The sending of and setting user-agent has not changed in many years (maybe 15?), which is partly why I have a hard time to suspect thhat this is a libcurl regression.

But I've been wrong before. jay commented on Dec 13, 2020 jay on Dec 13, 2020 Member More actions I can't think of any other report like this. You could bisect . bagder commented on Dec 16, 2020 bagder on Dec 16, 2020 Member More actions I don't think we can do anything about this issue without either a way to reproduce ourselves, or a very detailed description of exactly what the app does (libcurl-wise) when it fails.

Flameborn commented on Dec 17, 2020 Flameborn on Dec 17, 2020 Author More actions I have raised an issue for the Transmission client to request more information, as I believe they can provide details on how libcurl is used in the background. sveiki1 commented on Jan 2, 2021 sveiki1 on Jan 2, 2021 More actions Can confirm that I'm experiencing the same issue on Arch Linux ARM and Transmission. Issue seems to be present in: curl-7.73.0-1-armv7h.pkg.tar.xz (SHA-1: 49069eb3d5c1ffa84a15d958f2bd13a1f3598626) curl-7.74.0-1-armv7h.pkg.tar.xz (SHA-1: 1fa01e39f2bfea3f70f69d50438dce478bce9026) Downgrading to curl-7.67.0-3-armv7h.pkg.tar.xz (SHA-1: cc5d4f89e05a945a74bfce36f84786eb9e68e64d) seems to be a workaround.

I was unable to test other versions as those were the only ones present in the pacman cache in my machine. DontWorryScro commented on Jan 2, 2021 DontWorryScro on Jan 2, 2021 More actions +1 to confirm this is an issue. I'm getting intermittent "banned client" errors due to this. Edit: Using rTorrent:0.9.6/0.13.6 bagder commented on Jan 2, 2021 bagder on Jan 2, 2021 Member More actions Adding more "me toos" to this issue doesn't help.

We need more details . For example, show us the full HTTP requests done with a working libcurl and one with the problematic request? Perhaps even going so far to bisect to the exact libcurl change that introduced the problem. No other users report these problems and I libcurl is used quite widely. 17 remaining items bagder commented on Jan 5, 2021 bagder on Jan 5, 2021 Member More actions Please try out #6417 if you can build a local libcurl.

It is a fairly small patch. It fixes the problem in my tests. andreygursky commented on Jan 5, 2021 andreygursky on Jan 5, 2021 More actions I've just built current git master, which fails the test. After applying the patch I've let the test running for 7 minutes without facing the bug. Looks good, thanks! Reacted by Daniel Stenberg, Verwar and Stefan Karpinski Verwar commented on Jan 5, 2021 Verwar on Jan 5, 2021 More actions Glad @jay and @andreygursky helped with making it reproduce-able.

It would probably take me a bit longer. I hope my info helped speed things up. I've build curl with the fix and can confirm the issue is now gone (even with transmission). Thanks @bagder Flameborn commented on Jan 5, 2021 Flameborn on Jan 5, 2021 via email Author More actions I can confirm. The issue is gone here as well when using the patched build. Thank you very much for investigating this and for the quick fix. … On 2021.

Jan 5., at 16:21, Arjan ***@***.***> wrote: Glad @jay < https://github.com/jay > and @andreygursky < https://github.com/andreygursky > helped with making it reproduce-able. It would probably take me a bit longer. I hope my info helped speed things up. I've build curl with the fix and can confirm the issue is now gone (even with transmission). Thanks @bagder < https://github.com/bagder > — You are receiving this because you authored the thread.

Reply to this email directly, view it on GitHub < #6312 (comment) >, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AAHLD4GSEYARUAKVGRHSMY3SYMVBFANCNFSM4UYIGM7Q >. bagder closed this as completed

The rest of this page is on the live site.