On Thu, 31 Jul 2003, Serge Semashko wrote:

> DS> I'm thrilled to see that my proxy adjustments in the NTLM code worked that
> DS> nicely, as I haven't been able to test them.

> I see. I just was surprised because everything to support proxies is already
> in the code but is currently disabled, now I get your point. I can test curl
> on NTLM proxy server and also check Digest and Basic authentication for web
> server.

Neato, you rock Serge! We can hopefully get someone else to help us get the
Digest authentication going on proxies later.

> I just made an assumption that CURLOPT_HTTPAUTH option is supposed to select
> just security level no matter we connect a web server or proxy. Well, I was
> wrong, adding an option like CURLOPT_PROXYAUTH working similar to
> CURLOPT_HTTPAUTH will add more configurability (proxies are usually located
> in the local network, so they can have relaxed security settings).

Well, even if you need NTLM for your proxy you might still need Basic or
Digest etc for the remote host. They both work independently of each other.

> The code that is currently used to authenticate access to web pages can be
> reused for proxies with almost no changes. Probably the current code that
> does basic authentication on proxies will be not needed at all.
>
> DS> Would you be able to work a bit more on your patch to introduce this?
> Yes, I'm working on it now and will post a patch a bit later.

Great!

-- 
 Daniel Stenberg -- curl: been grokking URLs since 1998
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01