The problem might be on the client side. I recall seeing delays in SSH
handshakes due to the client checking the certificate revocation list
(CRL). It is a request to some server on the internet and my machine was
in a private network, so it had to timeout since the CRL server was not
reachable. Sorry if this isn't it.

On Tue, Feb 14, 2017 at 1:19 PM, Daniel Stenberg <daniel_at_haxx.se> wrote:

> On Tue, 14 Feb 2017, Praveen Pvs wrote:
>
> Today we have ran with libCURL version 7.52.1 on our terminal. The results
>> are better compared to previous version of CURL which we used. Instead of 1
>> sec, there is delay of 600ms(0.6sec) between the Client received the ACK
>> and the Client sent the HELLO to the server. We have tried multiple times
>> and this delay of 600ms is observed.
>>
>
> Well, and we have that bug in 7.52.1 that makes it sometimes wait without
> acting for a while. That's fixed in current master.
>
> It will be observed with any URL which does SSL handshake. We have tried
>> with Google.com also and this delay is observed.
>>
>
> Not for me.
>
> From my development machine, running curl from current git master built
> against OpenSSL 1.1.0d, "curl https://google.com" connects, handshakes
> TLS and gets the 302 response back in about 80 milliseconds. No 600ms wait
> here.
>
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
> Etiquette: https://curl.haxx.se/mail/etiquette.html
>

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2017-02-14