Alibek wrote:
> Curl 7.24 undergoes withs state transitions:
> GDCurl: STATE: WAITPROXYCONNECT => WAITCONNECT
> GDCurl: STATE: WAITCONNECT => PROTOCONNECT
> while Curl 7.38 goes from WAITPROXYCONNECT to WAITCONNECT and then remains
> stuck in this state.
> any ideas what could be root cause of this error?
> Perhaps new Curl requires some explicit configuration? or it could be some
> inner regression?

I *think* I git-bisected this to the following commit:

commit a4cece3d47cf092da00cf9910e87bb60b9eff533
Author: Daniel Stenberg <daniel_at_haxx.se>
Date: Sat Jul 19 23:58:58 2014 +0200

    CONNECT: Revert Curl_proxyCONNECT back to 7.29.0 design
    
    This reverts commit cb3e6dfa3511 and instead fixes the problem
    differently.
    
    The reverted commit addressed a test failure in test 1021 by simplifying
    and generalizing the code flow in a way that damaged the
    performance. Now we modify the flow so that Curl_proxyCONNECT() again
    does as much as possible in one go, yet still do test 1021 with and
    without valgrind. It failed due to mistakes in the multi state machine.
    
    Bug: http://curl.haxx.se/bug/view.cgi?id=1397
    Reported-by: Paul Saab

Could you try testing with revision d242839af8511b389f0edd6519bdae6cd860e8a9 to confirm? Thanks!
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2014-10-08