Well, running curl by itseld seem to have the same issue. The
webserver send us a 503 with too many connection (and I see it in my
snoop in wireshark) but yet curl seems to still be waiting somehow for
something

Emmanuel
On Sep 2, 2009, at 2:10 PM, Daniel Stenberg wrote:

> On Wed, 2 Sep 2009, Emmanuel Pinault wrote:
>
> Please don't top-post.
>
>> Interesting .. Sounds like something is not done correctly then on
>> curb.. Also I noticed that receiving a 503 with no body caused curb
>> to keep waiting forever....
>>
>> Would that be normal? Doesn't curl easy handle that automatically
>> or this is something that the curb dev would have to handle
>
> It should be handled automatically by libcurl, yes. Also, another
> test is to use the curl command line tool as that is using libcurl
> internally so it's a good test to see how another libcurl-using app
> behaves.
>
> --
>
> / daniel.haxx.se
Received on 2009-09-03