title: Gem Update System - Catch 22 with 302 redirects
body: <p>If I try to install any gem on my server then I get a 302 redirect e.g.</p>
  
  <pre><code>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
  </code></pre>
  
  <p>An article on rubygems suggests doing a gem update --system</p>
  
  <p><a href="http://help.rubygems.org/kb/rubygems/why-do-i-get-http-response-302-or-301-when-installing-a-gem" rel="nofollow">http://help.rubygems.org/kb/rubygems/why-do-i-get-http-response-302-or-301-when-installing-a-gem</a></p>
  
  <pre><code>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)
  </code></pre>
  
  <p>which is of course just an update of the gem itself.</p>
  
  <p>I'm running rubygems 1.3.1
  The latest version is 1.6.1</p>
  
  <p>Is there a way I can update Rubygems without getting caught in my 302 redirect trap.</p>
  
  <p>Regards,</p>
  
  <p>Kevin.</p>