From: Jim Freeze <jim@...>
Date: 2005-09-29T05:17:45+09:00
Subject: Re: gems is a language change, not a pkging system (Re: Require Namepaces and RubyGems' effect on LoadPath problem)

I have got gems to work from behind an authenticated proxy.
I set the proxy env variable:

   setenv http_proxy http://my.work.proxy:portnum

and gems runs as usual. On a rare occasion, the proxy won't
have my password cached, so to get around this I just do:

  curl -o --proxy-user `whoami` --proxy my.work.proxy ftp://ftp.some.small.file

from the commandline and then run the gem command again.
Gem now works without the password -- straight through the proxy.
I discovered this by mistake. Not sure if it is a bug in the proxy server
or not.

Also, notice that gem wants the http:// and curl does not when
specifying the proxy.

HTH

--
Jim Freeze