-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebUI API: setShareLimits method returns status code 400 #20110
Comments
I'm seeing the same issue on 4.6.2 using a script that previously worked (not sure which version it worked on). I also tried submitting the request with form data, as that was the fix for a different endpoint, but that didn't work either.
|
I figured out that the last version where this API method still worked was v4.5.5. So the issue must have been caused by something in the v4.6.0 release. |
#19294 has added one more parameter to |
I see, thanks! Adding the Here is my now working API request:
I appreciate your reply, but shouldn't this have been communicated in the release notes and the WebUI API reference? I was pretty stumped until now and was unable to find any resources pointing me to this solution. And in general, would it not be helpful to include a short error message in the API response, something like " I'll gladly contribute this info to the wiki myself, once I figure out how that works. |
qBittorrent & operating system versions
qBittorrent: v4.6.2 (64-Bit)
Operating System: Raspberry Pi OS / Debian GNU/Linux 11 (bullseye)
Qt: 6.6.1
libtorrent: 2.0.9.0
What is the problem?
Trying to use the
setShareLimits
API method no longer works and currently returns "400 - Bad Request". I used the same request previously in a python script, which used to work as expected. I can verify that my last successful call to that API method was on November 11th 2023, but I can't pinpoint what version I was using back then, although I do update fairly regularly. I have not changed the way I call that method since.I have tried out using other API methods, like
/torrents/addTags
, using the same torrent hash and session cookie, and that still succeeds as expected.Steps to reproduce
Additional context
cURL Snippet generated by Postman:
<< removed irrelevant logs and preferences >>
The text was updated successfully, but these errors were encountered: