yep, I fully agree. I could not reproduce it with standalone app. 
actual app injects its own sockets, filesystem and i have also customized 
kerberos build. Also, several threads (each with easy handle and one single 
thread on select) and several parallel http requests are running and it happens 
in the midst of them. 
so, it is hard to reproduce it in standalone case (i did build standalone app 
and it works fine). one of my theories is that Curl uses preconnected sockets 
in such a way that somewhere socket state is not taken into account. i patched 
Curl in few places hoping to fix it, but it di not help.
i decided to wait for 7.39. my migration from 7.24 to 7.37 is already a big 
jump.
however, i will keep thinking and experimenting and let you immediately if I 
find something...
but in any case, thanks for following up abd helping :)

> On 21 Oct 2014, at 23:36, Daniel Stenberg <[email protected]> wrote:
> 
>> On Wed, 15 Oct 2014, Alibek Joraev wrote:
>> 
>> I tried my test with Curl 7.37.0 and it works fine.  so this problem occurs
>> only in 7.38.0
> 
> Exactly, that's because commit a4cece3d47cf was made for 7.38.0. We've 
> already concluded that.
> 
> The question is why it fails, or how it should be fixed. I can't repeat your 
> problem and you haven't described it with details enough for me to figure it 
> out in my end.
> 
> -- 
> 
> / daniel.haxx.se
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette:  http://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html

Reply via email to