You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would make the library more flexible if the Uploader could be given a requests Session object which it uses to make all requests.
Custom requests sessions can be used for many things. For example, I use them myself to capture all 401 Unauthorized errors when my tokens are expired, make sure I'm re-authenticated and repeat the request. I've seen others use them to fix a URL base or adding custom headers.
Would tus-py-client maintainers be open to providing the ability to initialize an Uploader with a custom requests.Session object to enable use cases like this?
The text was updated successfully, but these errors were encountered:
Maybe it is not clear from the initial comment, but I would be willing to spend time myself implementing the feature, if you think it would be a good idea.
It would make the library more flexible if the Uploader could be given a requests Session object which it uses to make all requests.
Custom requests sessions can be used for many things. For example, I use them myself to capture all 401 Unauthorized errors when my tokens are expired, make sure I'm re-authenticated and repeat the request. I've seen others use them to fix a URL base or adding custom headers.
Would
tus-py-client
maintainers be open to providing the ability to initialize anUploader
with a customrequests.Session
object to enable use cases like this?The text was updated successfully, but these errors were encountered: