-
Notifications
You must be signed in to change notification settings - Fork 14
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
401 Client Error: Unauthorized for url #10
Comments
Suppose, you're right in your point about it could not refresh the token. Gonna research it deeply.
I think it's because the token is wrong. If you provide the correct one or just drop it off, it would work as expected. At least, I clicked on the link from the traceback and got a |
Thanks for a fast reply. Looking forward for a fix, now I'm just catching 401 exceptions and reauthenticate your storage manually but it's a dirty way. |
Well, if it works, who cares? :) BTW... Maybe if you have some time for that, can you please fork the app and put some loggers there to get what's happening there? What data is sent, timestamps, etc. After all, you have a working stand reproducing an error :) Not sure if I can repeat it fast. |
My inner perfectionist :) I'll try to investigate this problem deeper in the next days and send you a pull request with fix |
Would be great!
|
After some debugging I didn't found any reason why I'm getting those 401 errors. So I just added a check to reauthenticate and repeat request if needed. |
reauthenticate on unexpected 401 errors, fix of #10
Hi. I'm using your storage as a default file storage. I'm reading file content in some celery tasks and everything works ok, but after some moment I'm starting to get HTTP 401 Error. After restarting celery the error disappears but on the next day it's come back.
It's looks like your Auth class for some reason doesn't reauthenticate after token expired. It's weird because the container is public and file content can be accessed without authentication.
I'm using Python 3.7.6 with Django 2.2.12 and django-selectel-storage 1.0.0
The text was updated successfully, but these errors were encountered: