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.

Sign up for GitHub

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

Jump to bottom

Handle Refresh header as a redirect #465

Open
JustAnotherArchivist opened this issue Apr 17, 2021 · 0 comments
Open

Handle Refresh header as a redirect #465

JustAnotherArchivist opened this issue Apr 17, 2021 · 0 comments
Labels
enhancement

Comments

@JustAnotherArchivist
Copy link
Contributor

A Refresh header is effectively a (lagged) redirect. However, unlike on a 30# response, wpull does not follow the Refresh header unless recursion is enabled (and the URL isn't filtered by other means). I think it should treat it like a normal redirect.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JustAnotherArchivist