{"id":151118,"date":"2025-12-10T17:11:54","date_gmt":"2025-12-10T15:11:54","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-nginx-1-29-4-s-podderzhkoj-ech-i-vzaimodejstviya-s-bekendami-po-http-2-0"},"modified":"2025-12-10T17:11:54","modified_gmt":"2025-12-10T15:11:54","slug":"vypusk-nginx-1-29-4-s-podderzhkoj-ech-i-vzaimodejstviya-s-bekendami-po-http-2-0","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-nginx-1-29-4-s-podderzhkoj-ech-i-vzaimodejstviya-s-bekendami-po-http-2-0","title":{"rendered":"Release of nginx 1.29.4 with support for ECH and communication with backends via HTTP\/2.0.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of the main branch of nginx 1.29.4 has been published, continuing the development of new features. Only changes related to fixing serious bugs and vulnerabilities are made in the concurrently supported stable branch 1.28.x. Subsequently, a stable branch 1.30 will be formed based on the main branch 1.29.x. The project code is written in the C language and is distributed under the BSD license. <\/p>\n
In the new release: <\/p>\n
\n
Support for the HTTP\/2 protocol has been added to the ngx_http_proxy module, allowing the use of HTTP\/2 when accessing backends.\n
Support for the TLS extension ECH (Encrypted ClientHello) has been added, continuing the development of the ESNI (Encrypted Server Name Indication) extension and used for encrypting information about TLS session parameters, such as the requested domain name. The key distinction between ECH and ESNI is that while ESNI encrypts individual fields, ECH encrypts the entire ClientHello TLS message, which helps to prevent leaks through fields not covered by ESNI, such as the PSK (Pre-Shared Key) field. The use of ECH is enabled by specifying the ECH configuration file ECHConfig in PEM format in the «ssl_ech_file» directive. Support is available when using OpenSSL builds with ECH.\n
The rules for checking the host and port in the request text, the «Host» header, and the «:authority» pseudo-header have been aligned with the requirements of RFC 3986.\n
Specifying a single newline character as the terminating sequence in chunked requests or response bodies is now treated as an error.\n
A crash has been fixed when using HTTP\/3 with OpenSSL 3.5.1+.\n
A crash of the worker process has been resolved when using the try_files and proxy_pass directives simultaneously with a URI. <\/ul>\n