But so far I haven't received any error reports. PS: I'm wondering if libssh2 is also affected by the change in behavior with OpenSSL 3. If ((sslError = SSL_ERROR_SYSCALL & ::ERR_peek_last_error() = 0)) //EOF: only expected for HTTP/1.0 If (sslError = SSL_ERROR_SSL & ERR_GET_REASON(ec) = SSL_R_UNEXPECTED_EOF_WHILE_READING) //EOF: only expected for HTTP/1.0 Maybe it's to add OpenSSL version-dependent code like: So I'm not sure what the best fix for curl is. It seems, just adding SSL_OP_IGNORE_UNEXPECTED_EOF creates other problems with libcurl (=> empty directory listings) I made a quick test (=hack) without much understanding of the consequences in libcurl. Maybe this should be added to () to continue with the old EOF handling? I don't have a test server myself, but one of my software's users has: The unexpected EOF seems to only affect some (not well-behaved?) servers. The "unexpected eof while reading" is back in OpenSSL 3, as expected in … /curl/curl/issues/5138
0 kommentar(er)
