On Fri, Dec 27, 2002 at 07:06:58PM +0100, Daniel Stenberg wrote:
> On Thu, 26 Dec 2002, Domenico Andreoli wrote:
>
> > as i understood reading the full bug report (available at
> > bugs.debian.org/114228) it was a bug in your proxy. am i wrong?
> >
> > could you and daniel proceed further in the develop of the matter?
>
> IMHO:
>
> I have yet to see any evidence that this is a curl bug. The whole bug history
> as seen at bugs.debian.org/114228 shows this being a stupid proxy that does
> not follow/obey HTTP standards.

You know [much] more about this than I do. I am just sad that I can use any
and all of the following without any issues:
 -- mozilla, galeon and friends
 -- GNU wget
 -- all my own Perl code [e.g. Finance::YahooQuote as well as smtm and
    beancounter which use it ] thanks to logic in libwww-perl (aka LWP)

Curl is a *great* library, it would be nice to be able to use it too.

> Yes, curl should possibly be adjusted to work with it, particularly when
> other open source software manages to work with it, but I still can't see how
> this is a bug. I even can't see what we need to adjust to make it work in
> such a away.
>
> curl works fine with proxies all over the world and has done so for many
> years. This is a very rare exception.

The shop I work for is a Fortune100 with fairly decent equipment. I don't
think that this is a fly-by-night proxy. If you can think of a way in which
I can help you, let me know.

As for the Debian bug report, close it then. Upstream should IMHO always
have the last word.

Dirk

-- 
Prediction is very difficult, especially about the future. 
				             -- Niels Bohr
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf