If I try to install any gem on my server, then I get a 302 redirect, for example.
gem install clickatell -V GET http://rubygems.org/latest_specs.4.8.gz 302 Found HEAD http://rubygems.org/specs.4.8.gz connection reset after 2 requests, retrying HEAD http://rubygems.org/specs.4.8.gz 302 Found
An article on rubygems suggests updating gem - system
http://help.rubygems.org/kb/rubygems/why-do-i-get-http-response-302-or-301-when-installing-a-gem
gem update --system -V Updating RubyGems GET 302 Found: http://gems.rubyforge.org/latest_specs.4.8.gz connection reset after 2 requests, retrying HEAD 302 Found: http://gems.rubyforge.org/specs.4.8.gz connection reset after 2 requests, retrying HEAD 302 Found: http://gems.rubyforge.org/yaml ERROR: http://gems.rubyforge.org/ does not appear to be a repository ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError) Errno::ETIMEDOUT: Connection timed out - connect(2) (http://gems.rubyforge.org/yaml)
which is, of course, just an update of the gem itself.
I am running rubygems 1.3.1. The latest version is 1.6.1.
Is there a way to update Rubygems without falling into the 302 redirect trap.
Hello,
Kevin.
source share