alex/manage
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(qbittorrent): show set-cookie presence in login diagnostic

Browse Source 
When the login endpoint returns an unexpected response (e.g. a 204 No Content
with no body), the diagnostic now reports whether a Set-Cookie header was
present. That single fact tells us whether qBittorrent attempted to establish
a session at all — distinguishing "qBittorrent answered weirdly" from
"something in the proxy path answered before qBittorrent" (e.g. a 204 from a
misrouted reverse proxy), which is the key clue when diagnosing login failures
behind a proxy.

42/42 qBittorrent + credential-tester tests pass; ruff clean.
This commit is contained in:
Developer
2026-07-12 10:35:30 +00:00
parent 6d46de26c4
commit b9a79b85d1
3 changed files with 8 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
backend/src/media_library_viewer_api/clients/.pi-map.index.md
+1 -1
View File
@@ -2,7 +2,7 @@
dir: backend/src/media_library_viewer_api/clients
## role
Provides external service integration clients (API wrappers and remote/local command executors) for media library data aggregation and system monitoring.
Collection of API and protocol client wrappers for external services (Jellyfin, Authentik, Jellyseerr, qBittorrent, SSH, local execution) with shared HTTP timeout configuration.
## parent
index: backend/src/media_library_viewer_api/.pi-map.index.md
map: backend/src/media_library_viewer_api/.pi-map.md