mirror of
https://github.com/curl/curl.git
synced 2024-12-15 06:40:09 +08:00
wolfssl: failing to set a session id is not reason to error out
... as it is *probably* just timed out. Reported-by: Francisco Munoz Closes #7358
This commit is contained in:
parent
ae8e11ed5f
commit
1e488d38c9
@ -494,15 +494,11 @@ wolfssl_connect_step1(struct Curl_easy *data, struct connectdata *conn,
|
||||
&ssl_sessionid, NULL, sockindex)) {
|
||||
/* we got a session id, use it! */
|
||||
if(!SSL_set_session(backend->handle, ssl_sessionid)) {
|
||||
char error_buffer[WOLFSSL_MAX_ERROR_SZ];
|
||||
Curl_ssl_sessionid_unlock(data);
|
||||
failf(data, "SSL: SSL_set_session failed: %s",
|
||||
ERR_error_string(SSL_get_error(backend->handle, 0),
|
||||
error_buffer));
|
||||
return CURLE_SSL_CONNECT_ERROR;
|
||||
Curl_ssl_delsessionid(data, ssl_sessionid);
|
||||
infof(data, "Can't use session ID, going on without\n");
|
||||
}
|
||||
/* Informational message */
|
||||
infof(data, "SSL re-using session ID\n");
|
||||
else
|
||||
infof(data, "SSL re-using session ID\n");
|
||||
}
|
||||
Curl_ssl_sessionid_unlock(data);
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user