[Rubygems-developers] Good new on authenticating proxies!
chad at chadfowler.com
Mon Feb 7 20:07:08 EST 2005
Great, Assaph! I wonder how we should get the word out re: using
apserver. Maybe we can throw it in the README.
Thanks much for your patch! I'll apply it this evening after dinner.
Regarding the Zlib BufError, it's strange that I have the exact same
configuration as you and don't get the error. I hate that kind of bug.
On 07-Feb-05, at 6:30 PM, Assaph Mehr wrote:
> Hi Guys,
> Finally made gems work through our Corporate NTLM Authenticating Proxy!
> There are two issues:
> 1. NTLM Authentication
> I installed http://apserver.sourceforge.net/, which is a local
> proxy (on my machine) that does the NTLM authentication with the
> corporate one. I just point gems etc to this proxy as a
> non-authenticating one. It's written in python, but I won't hold it
> against it :-)
> 2. Gems patch
> I still got an error using gems through the proxy. The attached
> patch fixes this (done against CVS head).
> While this is pehaps not an ideal solution, it provides a workaround
> for anyone who's behind an NTLM proxy.
> ps Re the error that was reported on ruby-talk with installing
> rubygems-update (Zlib::BufError), I get the same error. It's gems
> 0.8.4 (or latest CVS), ruby 1.8.2 (2004-11-06) [i386-mswin32] with
> the 1-Click installer on WinXP. I know ZLib is installed and working
> Rubygems-developers mailing list
> Rubygems-developers at rubyforge.org
More information about the Rubygems-developers