aboutsummaryrefslogtreecommitdiff
path: root/src/stream/ngx_stream_proxy_module.c
diff options
context:
space:
mode:
authorSergey Kandaurov <pluknet@nginx.com>2021-08-10 23:43:17 +0300
committerSergey Kandaurov <pluknet@nginx.com>2021-08-10 23:43:17 +0300
commit5155845ce4453a07d60e2ce43946c9181bc311fa (patch)
tree48bb8c3cd0d9097ab286634187d5f257b75ad998 /src/stream/ngx_stream_proxy_module.c
parent3df7efd34b26328c94149b6828ea22bb73ce00a2 (diff)
downloadnginx-5155845ce4453a07d60e2ce43946c9181bc311fa.tar.gz
nginx-5155845ce4453a07d60e2ce43946c9181bc311fa.zip
SSL: use of the SSL_OP_IGNORE_UNEXPECTED_EOF option.
A new behaviour was introduced in OpenSSL 1.1.1e, when a peer does not send close_notify before closing the connection. Previously, it was to return SSL_ERROR_SYSCALL with errno 0, known since at least OpenSSL 0.9.7, and is handled gracefully in nginx. Now it returns SSL_ERROR_SSL with a distinct reason SSL_R_UNEXPECTED_EOF_WHILE_READING ("unexpected eof while reading"). This leads to critical errors seen in nginx within various routines such as SSL_do_handshake(), SSL_read(), SSL_shutdown(). The behaviour was restored in OpenSSL 1.1.1f, but presents in OpenSSL 3.0 by default. Use of the SSL_OP_IGNORE_UNEXPECTED_EOF option added in OpenSSL 3.0 allows to set a compatible behaviour to return SSL_ERROR_ZERO_RETURN: https://git.openssl.org/?p=openssl.git;a=commitdiff;h=09b90e0 See for additional details: https://github.com/openssl/openssl/issues/11381
Diffstat (limited to 'src/stream/ngx_stream_proxy_module.c')
0 files changed, 0 insertions, 0 deletions