Skip to content
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

Long-lived clients do not handle session cookie expiration #86

Closed
JoshGlazebrook opened this issue Oct 19, 2020 · 2 comments · Fixed by #87
Closed

Long-lived clients do not handle session cookie expiration #86

JoshGlazebrook opened this issue Oct 19, 2020 · 2 comments · Fixed by #87
Labels

Comments

@JoshGlazebrook
Copy link

QBittorrent seems to have a default timeout of 3600 seconds (1 hour) for sessions when logging into the webui.

Based on the code, it does an initial login and for each request done with the same client instance, if there is a cookie set locally this._sid it sets it as the Cookie header. However after the cookie expires, it doesn't re-login, it just keeps using the same expired cookie.

Potential solution for this is to make note of the expiration of the cookie itself and re-login when needed?

@scttcper
Copy link
Owner

🎉 This issue has been resolved in version 2.8.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@Schaka
Copy link

Schaka commented May 22, 2023

Just wanted to say thanks for this issue as I couldn't find session expiry time in the docs and had a similar issue with the using the API directly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants