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

Explicit redirect handling #23

Open
AMDmi3 opened this issue Jul 2, 2019 · 0 comments
Open

Explicit redirect handling #23

AMDmi3 opened this issue Jul 2, 2019 · 0 comments

Comments

@AMDmi3
Copy link
Member

AMDmi3 commented Jul 2, 2019

To be more consistent and informative, and also to obey RPS limits more strictly, redirects are needed to be handled explicitly. E.g.

  • aiohttp's automatic redirect following should be disabled
  • on redirect, the target needs to be added to the links table if it's not yet there and checked as a normal link (need to think of last_seen propagation and clever next_check handling, so redirect chains are usually checked at once).
  • repology /link/ viewer should be modified accordingly
  • there should be some sort of bad status propagation from target to redirect source (with loop detection) (or should we do in on the fly?)
  • could add id column to links table,

This would allow to handle http->ftp redirects btw.

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

No branches or pull requests

1 participant