comparison text/en/CHANGES @ 2748:1d3a8a4adec2

nginx-1.21.1
author Maxim Dounin <mdounin@mdounin.ru>
date Tue, 06 Jul 2021 18:04:36 +0300
parents a7a36efd10af
children 137bb01e7a3b
comparison
equal deleted inserted replaced
2747:42fb92e582db 2748:1d3a8a4adec2
1
2 Changes with nginx 1.21.1 06 Jul 2021
3
4 *) Change: now nginx always returns an error for the CONNECT method.
5
6 *) Change: now nginx always returns an error if both "Content-Length"
7 and "Transfer-Encoding" header lines are present in the request.
8
9 *) Change: now nginx always returns an error if spaces or control
10 characters are used in the request line.
11
12 *) Change: now nginx always returns an error if spaces or control
13 characters are used in a header name.
14
15 *) Change: now nginx always returns an error if spaces or control
16 characters are used in the "Host" request header line.
17
18 *) Change: optimization of configuration testing when using many
19 listening sockets.
20
21 *) Bugfix: nginx did not escape """, "<", ">", "\", "^", "`", "{", "|",
22 and "}" characters when proxying with changed URI.
23
24 *) Bugfix: SSL variables might be empty when used in logs; the bug had
25 appeared in 1.19.5.
26
27 *) Bugfix: keepalive connections with gRPC backends might not be closed
28 after receiving a GOAWAY frame.
29
30 *) Bugfix: reduced memory consumption for long-lived requests when
31 proxying with more than 64 buffers.
32
1 33
2 Changes with nginx 1.21.0 25 May 2021 34 Changes with nginx 1.21.0 25 May 2021
3 35
4 *) Security: 1-byte memory overwrite might occur during DNS server 36 *) Security: 1-byte memory overwrite might occur during DNS server
5 response processing if the "resolver" directive was used, allowing an 37 response processing if the "resolver" directive was used, allowing an