On Wed, 3 Oct 2001, Dirk Eddelbuettel wrote:

> > Are you saying that this doesn't return any HTML for you? It would rather
> > indicate a problem with your proxy, as I see it!
>
> Correct. I ask this simple.c variant to dump all html into a file ... and
> the resulting file has length zero without CURLOPT_USERPWD being set.

Uh. That is so incorrect behavior...

> Could well be a proxy server bug. I am fully ignorant of the details and
> RFCs.

I understand your view of this. I would have the same in your shoes.

> But cnn.com doesn't need my name/password, so that should not have to
> fall under Authorization.

Exactly. And in my end it doesn't fail, neither without nor with proxy as I
described.

> > And the CNN server returned the following headers:

 [snip]

> Hm, I don;t get those. Special cmd line option needed to see them?

Yeps, use -i to get them before the actual body or use -I to make a HEAD
request instead of GET which will only get the headers.

It is possible that your proxy returns useful information in the headers.

> That's why I tried to be careful in my initial bug report. It is
> conceivable that the firewall/proxy server used here is wrong. Dunno. But
> it works with a good number of other apps/libs. If it helped, I could
> show you what I need for Perl's LWP module.

This really bugs me. Can you dig up what their request looks like?

> If you see no fault in your code, it might be good enough to modify the
> curl_easy_setopt manual page entry for CURLOPT_USERPWD to add a hint that
> this option may be needed with some proxy-auth firewalls in addition to
> the CURLOPT_PROXYUSERPWD option.

If this is the conclusion we end up, then yes I will do that.

I'm still not convinced nor comfortable with the fact that your work-around
should be required for you to make it work. The fact that other tools have no
problems indicate that they do things differently and then there might be a
problem in libcurl after all anyway.

What if you telnet to your proxy and enter that request manually?

I brought up my RFC2616 again and browsed through these sections, but I
didn't see anything new regarding this.

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/