On 10/27/2015 2:09 AM, KS Lee wrote:
> schannel: Curl_read_plain returned CURLE_RECV_ERROR

That you have the same issue with WinSSL as you do OpenSSL leads me to
believe this isn't a problem with either. You don't have this problem
without SSL? I apologize if this was answered already but I can only
find part of the thread now. Is it possible that the reason you don't
see an issue over a proxy like Fiddler is because you didn't use it
enough to observe the issue there? In other words just because it
appears to work fine through Fiddler a few times isn't the same as your
normal use.

You wrote in another e-mail "Wireshark traces for the non-proxy
scenario, it is showing a TCP disconnecting from libcurl, and then
reconnecting at every HTTP interaction with the web server. This is
normal behaviour, since keep-alive was not set." [1] Maybe the constant
reconnection is why the issue can be more readily observed without a
proxy. When you say keep alive are you referring to TCP keepalive or
sending an actual Keep-Alive in the header which shouldn't be necessary
with HTTP/1.1 since keepalive is the default?

[1]: http://curl.haxx.se/mail/lib-2015-10/0126.html
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2015-11-04