Update content
Feature：ngx_stream_set_module Feature: "proxy_cookie_flags" directive Bugfix: If the status code returned by the backend is 500, 502, 503, 504, 403, 404 or 429, the "stale if error" cache control extension will be applied incorrectly Bugfix: If the cache is used and the backend returns a response with a "Vary" header line, the "[crit] cache file... has too long header" message may appear in the log Workaround: When using OpenSSL 1.1.1, the message "[crit] SSL_write() failed" may appear in the log Bugfix: "SSL_shutdown() failed (SSL:... bad write retry)" message may appear in the log; This error has occurred in 1.19.2 Bugfix: If the "error_page" command is used to redirect the error of code 400 to the proxy location, a segment fault may appear in the work process when HTTP/2 is used Bugfix: Socket leak when using HTTP/2 and sub requests in the njs module
original text
Changes with nginx 1.19.3 29 Sep 2020 *) Feature: the ngx_stream_set_module. *) Feature: the "proxy_cookie_flags" directive. *) Feature: the "userid_flags" directive. *) Bugfix: the "stale-if-error" cache control extension was erroneously applied if backend returned a response with status code 500, 502, 503, 504, 403, 404, or 429. *) Bugfix: "[crit] cache file ... has too long header" messages might appear in logs if caching was used and the backend returned responses with the "Vary" header line. *) Workaround: "[crit] SSL_write() failed" messages might appear in logs when using OpenSSL 1.1.1. *) Bugfix: "SSL_shutdown() failed (SSL: ... bad write retry)" messages might appear in logs; the bug had appeared in 1.19.2. *) Bugfix: a segmentation fault might occur in a worker process when using HTTP/2 if errors with code 400 were redirected to a proxied location using the "error_page" directive. *) Bugfix: socket leak when using HTTP/2 and subrequests in the njs module.
