v1.15.2 fixes connection problems with qBittorrent-compatible download clients, including the long session cookies returned by rdt-client.
Fixed
- Session cookie values can now be up to 4,096 bytes. Previously, a cookie longer than 256 characters caused Jellydash to reject an otherwise successful login. Saved sessions use the same limit.
- A successful login without a usable cookie now gets its own error message instead of "The client rejected the credentials."
- The connection test accepts older compatible clients reporting qBittorrent 4.3.2 or newer within 4.x and Web API 2.7 or newer within 2.x. Versions below 4.6 also get additional checks of their transfer and torrent responses. Bare and quoted version responses are handled consistently.
- Recent activity handles unordered history responses from clients that ignore pagination. Jellydash sorts oversized pages locally and keeps the existing response-size, time and scan limits.
For rdt-client, choose qBittorrent as the client type and keep authentication enabled. Compatibility was checked against its current source and local HTTP fixtures; it has not yet been verified on the reporter's installation.
Thanks to @ForestSound for the detailed report and follow-up in #32.
Updating
This release adds no database migration or required settings.
For Compose installations:
docker compose pull && docker compose up -dFor a pinned image, use ghcr.io/themartz90/jellydash:1.15.2. On Unraid, use the normal container update.