Remove dependence on qBittorrent session cookie being named SID
#139
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The name of the qBittorrent session cookie is now configurable via qbittorrent/qBittorrent#18384.
My initial go at this simply allowed the user to declare the name of the cookie being used. However, this can only be done when
Client
is initialized. Therefore, if the cookie name is changed or just a different qBittorrent host shows up, then theClient
will need to be recreated altogether.This client strives to always establish a successful connection for any API request as long as the username/password is correct. This may be possible if qBittorrent exposed the name of the cookie via an API method....but either way, this strategy just removes the dependence on knowing what the session cookie is at all.