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

Gem::Mirror::Fetcher#handle_response doesn't handle 301 Moved Permanently responses #17

Closed
zettabyte opened this issue Feb 3, 2013 · 0 comments · Fixed by #18
Closed

Gem::Mirror::Fetcher#handle_response doesn't handle 301 Moved Permanently responses #17

zettabyte opened this issue Feb 3, 2013 · 0 comments · Fixed by #18

Comments

@zettabyte
Copy link
Contributor

So, just tried to use gem mirror and the attempt to grab the specs file failed since rubygems.org returned a 301 Moved Permanently HTTP response. Looks like the code in the Gem::Mirror::Fetcher#handle_response just needs to be updated to be able to handle this response and retry using the new URL in the returned Location header.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support "301 Moved Permanently" HTTP responses too.
1 participant
@zettabyte