~titusx/nginx/mainline : changes

~titusx/nginx/mainline » Changes from revision 7236

From Revision 6765 to 6746

Rev	Summary	Authors	Tags	Date
6765	Mail: proxy_smtp_auth directive. Mail: proxy_smtp_auth directive. The proxy_smtp_auth directive instructs nginx to authenticate users on backend via the AUTH command (using the PLAIN SASL mechanism), similar to what is normally done for IMAP and POP3. If xclient is enabled along with proxy_smtp_auth, the XCLIENT command won't try to send the LOGIN parameter.	Maxim Dounin		3 years ago
6764	Version bump. Version bump.	Maxim Dounin		3 years ago
6763	release-1.19.3 tag release-1.19.3 tag	Maxim Dounin		3 years ago
6762	nginx-1.19.3-RELEASE nginx-1.19.3-RELEASE	Maxim Dounin	release-1.19.3	3 years ago
6761	Updated OpenSSL used for win32 builds. Updated OpenSSL used for win32 builds.	Maxim Dounin		3 years ago
6760	Proxy: error checking for array init, missed in 7716:d6a5e14... Proxy: error checking for array init, missed in 7716:d6a5e14aa3e4. Found by Coverity (CID 1467637).	Maxim Dounin		3 years ago
6759	Userid: userid_flags fixup. Userid: userid_flags fixup. In 7717:e3e8b8234f05, the 1st bit was incorrectly used. It shouldn't be used for bitmask values, as it is used by NGX_CONF_BITMASK_SET. Additionally, special value "off" added to make it possible to clear inherited userid_flags value.	Maxim Dounin		3 years ago
6758	Resolver: improved error messages (ticket #2024). Resolver: improved error messages (ticket #2024).	Maxim Dounin		3 years ago
6757	Userid: userid_flags directive to set cookie flags. Userid: userid_flags directive to set cookie flags.	Maxim Dounin		3 years ago
6756	Proxy: added the "proxy_cookie_flags" directive. Proxy: added the "proxy_cookie_flags" directive.	Ruslan Ermilov		3 years ago
6755	Proxy: changed interface of some internal functions. Proxy: changed interface of some internal functions. This is in preparation for the next change. Also, moved optimization from ngx_http_proxy_rewrite_regex_handler() to ngx_http_proxy_rewrite().	Ruslan Ermilov		3 years ago
6754	Proxy: strengthen syntax checking for some directives. Proxy: strengthen syntax checking for some directives. The "false" parameter of the proxy_redirect directive is deprecated. Warning has been emitted since c2230102df6f (0.7.54). The "off" parameter of the proxy_redirect, proxy_cookie_domain, and proxy_cookie_path directives tells nginx not to inherit the configuration from the previous configuration level. Previously, after specifying the directive with the "off" parameter, any other directives were ignored, and syntax checking was disabled. The syntax was enforced to allow either one directive with the "off" parameter, or several directives with other parameters. Also, specifying "proxy_redirect default foo" no longer works like "proxy_redirect default".	Ruslan Ermilov		3 years ago
6753	Stream: set module. Stream: set module. Adds 'set' directive to the stream server context.	Pavel Pautov		3 years ago
6752	SSL: abort handshake on SSL_set_SSL_CTX() errors. SSL: abort handshake on SSL_set_SSL_CTX() errors. In rare cases, such as memory allocation failure, SSL_set_SSL_CTX() returns NULL, which could mean that a different SSL configuration has not been set. Note that this new behaviour seemingly originated in OpenSSL-1.1.0 release.	Sergey Kandaurov		3 years ago
6751	HTTP/2: run posted requests after reading body. HTTP/2: run posted requests after reading body. HTTP/2 code failed to run posted requests after calling the request body handler, and this resulted in connection hang if a subrequest was created in the body handler and no other actions were made.	Maxim Dounin		3 years ago
6750	HTTP/2: fixed segfault on DATA frames after 400 errors. HTTP/2: fixed segfault on DATA frames after 400 errors. If 400 errors were redirected to an upstream server using the error_page directive, DATA frames from the client might cause segmentation fault due to null pointer dereference. The bug had appeared in 6989:2c4dbcd6f2e4 (1.13.0). Fix is to skip such frames in ngx_http_v2_state_read_data() (similarly to 7561:9f1f9d6e056a). With the fix, behaviour of 400 errors in HTTP/2 is now similar to one in HTTP/1.x, that is, nginx doesn't try to read the request body. Note that proxying 400 errors, as well as other early stage errors, to upstream servers might not be a good idea anyway. These errors imply that reading and processing of the request (and the request headers) wasn't complete, and proxying of such incomplete request might lead to various errors. Reported by Chenglong Zhang.	Maxim Dounin		3 years ago
6749	SSL: disabled shutdown when there are buffered data. SSL: disabled shutdown when there are buffered data. This fixes "SSL_shutdown() failed (SSL: ... bad write retry)" errors as observed on the second SSL_shutdown() call after SSL shutdown fixes in 09fb2135a589 (1.19.2), notably when HTTP/2 connections are closed due to read timeouts while there are incomplete writes.	Maxim Dounin		3 years ago
6748	SSL: disabled shutdown after connection errors. SSL: disabled shutdown after connection errors. This fixes "SSL_shutdown() failed (SSL: ... bad write retry)" errors as observed on the second SSL_shutdown() call after SSL shutdown fixes in 09fb2135a589 (1.19.2), notably when sending fails in ngx_http_test_expect(), similarly to ticket #1194. Note that there are some places where c->error is misused to prevent further output, such as ngx_http_v2_finalize_connection() if there are pending streams, or in filter finalization. These places seem to be extreme enough to don't care about missing shutdown though. For example, filter finalization currently prevents keepalive from being used.	Maxim Dounin		3 years ago
6747	SSL: fixed event handling during shutdown. SSL: fixed event handling during shutdown. The c->read->ready and c->write->ready flags need to be cleared to ensure that appropriate read or write events will be reported by kernel. Without this, SSL shutdown might wait till the timeout after blocking on writing or reading even if there is a socket activity.	Maxim Dounin		3 years ago
6746	SSL: workaround for incorrect SSL_write() errors in OpenSSL ... SSL: workaround for incorrect SSL_write() errors in OpenSSL 1.1.1. OpenSSL 1.1.1 fails to return SSL_ERROR_SYSCALL if an error happens during SSL_write() after close_notify alert from the peer, and returns SSL_ERROR_ZERO_RETURN instead. Broken by this commit, which removes the "i == 0" check around the SSL_RECEIVED_SHUTDOWN one: https://git.openssl.org/?p=openssl.git;a=commitdiff;h=8051ab2 In particular, if a client closed the connection without reading the response but with properly sent close_notify alert, this resulted in unexpected "SSL_write() failed while ..." critical log message instead of correct "SSL_write() failed (32: Broken pipe)" at the info level. Since SSL_ERROR_ZERO_RETURN cannot be legitimately returned after SSL_write(), the fix is to convert all SSL_ERROR_ZERO_RETURN errors after SSL_write() to SSL_ERROR_SYSCALL.	Maxim Dounin		3 years ago