SSL_RECV: EOF is not an error here
The recent overhaul of the SSL recv function made this treat a zero returned from gnutls_record_recv() as an error, and this caused our HTTPS test cases to fail. We leave it to upper layer code to detect if an EOF is a problem or not.
This commit is contained in:
parent
cca192e58f
commit
2056ca9fea
@ -778,12 +778,6 @@ ssize_t Curl_gtls_recv(struct connectdata *conn, /* connection data */
|
|||||||
return -1;
|
return -1;
|
||||||
}
|
}
|
||||||
|
|
||||||
if(!ret) {
|
|
||||||
failf(conn->data, "Peer closed the TLS connection");
|
|
||||||
*curlcode = CURLE_RECV_ERROR;
|
|
||||||
return -1;
|
|
||||||
}
|
|
||||||
|
|
||||||
if(ret < 0) {
|
if(ret < 0) {
|
||||||
failf(conn->data, "GnuTLS recv error (%d): %s",
|
failf(conn->data, "GnuTLS recv error (%d): %s",
|
||||||
(int)ret, gnutls_strerror((int)ret));
|
(int)ret, gnutls_strerror((int)ret));
|
||||||
|
Loading…
x
Reference in New Issue
Block a user