与时俱进,精研业务
编者按:今天,抽时间将nginx 1.23.1升级到nginx 1.23.4,并附录官网对其功能迭代的说明。Changes with nginx 1.23.4 28 Mar 2023 *) Change: now TLSv1.3 protocol is

安装nginx 1.23.1以来,一直未对其版本升级。今天,抽时间将nginx 1.23.1升级到nginx 1.24.0,nginx 1.24.0错误日志里面已经部分支持中文提示了,如:
(10060: 由于连接方在一段时间后没有正确答复或连接的主机没有反应,连接尝试失败。)
(3: 系统找不到指定的路径。)
(2: 系统找不到指定的文件。)
现附录官网对其功能迭代的说明,大家有空可以慢慢探索体验。(nginx官网下载地址:http://nginx.org/en/download.html)
Changes with nginx 1.24.0 11 Apr 2023
*) 1.24.x stable branch.
Changes with nginx 1.23.4 28 Mar 2023
*) Change: now TLSv1.3 protocol is enabled by default.
*) Change: now nginx issues a warning if protocol parameters of a listening socket are redefined.
*) Change: now nginx closes connections with lingering if pipelining was used by the client.
*) Feature: byte ranges support in the ngx_http_gzip_static_module.
*) Bugfix: port ranges in the "listen" directive did not work; the bug had appeared in 1.23.3.
Thanks to Valentin Bartenev.
*) Bugfix: incorrect location might be chosen to process a request if a prefix location longer than 255 characters was used in the configuration.
*) Bugfix: non-ASCII characters in file names on Windows were not supported by the ngx_http_autoindex_module, the ngx_http_dav_module, and the "include" directive.
*) Change: the logging level of the "data length too long", "length too short", "bad legacy version", "no shared signature algorithms", "bad digest length", "missing sigalgs extension", "encrypted length too long", "bad length", "bad key update", "mixed handshake and non handshake data", "ccs received early", "data between ccs and finished", "packet length too long", "too many warn alerts", "record too small", and "got a fin before a ccs" SSL errors has been lowered from "crit" to "info".
*) Bugfix: a socket leak might occur when using HTTP/2 and the "error_page" directive to redirect errors with code 400.
*) Bugfix: messages about logging to syslog errors did not contain information that the errors happened while logging to syslog.
Thanks to Safar Safarly.
*) Workaround: "gzip filter failed to use preallocated memory" alerts appeared in logs when using zlib-ng.
*) Bugfix: in the mail proxy server.
Changes with nginx 1.23.3 13 Dec 2022
*) Bugfix: an error might occur when reading PROXY protocol version 2 header with large number of TLVs.
*) Bugfix: a segmentation fault might occur in a worker process if SSI was used to process subrequests created by other modules.
Thanks to Ciel Zhao.
*) Workaround: when a hostname used in the "listen" directive resolves to multiple addresses, nginx now ignores duplicates within these addresses.
*) Bugfix: nginx might hog CPU during unbuffered proxying if SSL connections to backends were used.
Changes with nginx 1.23.2 19 Oct 2022
*) Security: processing of a specially crafted mp4 file by the ngx_http_mp4_module might cause a worker process crash, worker process memory disclosure, or might have potential other impact (CVE-2022-41741, CVE-2022-41742).
*) Feature: the "$proxy_protocol_tlv_..." variables.
*) Feature: TLS session tickets encryption keys are now automatically rotated when using shared memory in the "ssl_session_cache" directive.
*) Change: the logging level of the "bad record type" SSL errors has been lowered from "crit" to "info".
Thanks to Murilo Andrade.
*) Change: now when using shared memory in the "ssl_session_cache" directive the "could not allocate new session" errors are logged at the "warn" level instead of "alert" and not more often than once per second.
*) Bugfix: nginx/Windows could not be built with OpenSSL 3.0.x.
*) Bugfix: in logging of the PROXY protocol errors.
Thanks to Sergey Brester.
*) Workaround: shared memory from the "ssl_session_cache" directive was spent on sessions using TLS session tickets when using TLSv1.3 with OpenSSL.
*) Workaround: timeout specified with the "ssl_session_timeout" directive did not work when using TLSv1.3 with OpenSSL or BoringSSL.
Changes with nginx 1.23.1 19 Jul 2022
*) Feature: memory usage optimization in configurations with SSL proxying.
*) Feature: looking up of IPv4 addresses while resolving now can be disabled with the "ipv4=off" parameter of the "resolver" directive.
*) Change: the logging level of the "bad key share", "bad extension","bad cipher", and "bad ecpoint" SSL errors has been lowered from "crit" to "info".
*) Bugfix: while returning byte ranges nginx did not remove the "Content-Range" header line if it was present in the original backend response.
*) Bugfix: a proxied response might be truncated during reconfiguration on Linux; the bug had appeared in 1.17.5.
本文标签:

专注执业领域事务
全力办理委托事项
扎实维护合法权益

24小时免费咨询
请输入您的联系电话,座机请加区号
