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
Should the project handle HTTP redirects? #1
Comments
I hesitated on that one but eventually it's more interesting to get the final destination. Maybe I should store somewhere that a redirect was issued though in order to be able to update the URL somehow. Thoughts? |
It can be interesting to know which type of redirects. Is it a temporary redirect and need to keep the original URI in the URI db, or is a permanent redirect and need to replace the original URI (assuming that people respect such a thing ;) ) Anyway food for thoughts: I had some sites doing a series of 5 redirects before reaching the final resource. Type of redirects I get:
All redirects are not HTTP
Some redirects are done just for login credentials ^_^ |
After some time in production, we need to handle both cases:
Reopened issues are the best 😉 |
Currently the requests is not handling the redirect.
Not sure if it's by choice or not.
I can make a pull request to add
, allow_redirects=True
except if it's by choice.The text was updated successfully, but these errors were encountered: