[Pkg-nginx-maintainers] Bug#821111: nginx: Failure to remove socket due to Debian's method of stopping

[吳宇萱/土撥鼠（Lisbeth Wu）]

According to the nginx changelog, it's been fixed in 1.19.1

part of changelog http://nginx.org/en/CHANGES

Changes with nginx 1.19.1                                        07 Jul 2020

    *) Change: the "lingering_close", "lingering_time", and
       "lingering_timeout" directives now work when using HTTP/2.

    *) Change: now extra data sent by a backend are always discarded.

    *) Change: now after receiving a too short response from a FastCGI
       server nginx tries to send the available part of the response to the
       client, and then closes the client connection.

    *) Change: now after receiving a response with incorrect length from a
       gRPC backend nginx stops response processing with an error.

    *) Feature: the "min_free" parameter of the "proxy_cache_path",
       "fastcgi_cache_path", "scgi_cache_path", and "uwsgi_cache_path"
       directives.
       Thanks to Adam Bambuch.
**) Bugfix: nginx did not delete unix domain listen sockets during
graceful shutdown on the SIGQUIT signal. *The last one which is indicate to the bug related
**

-- 
	
吳宇萱 / Lisbeth Wu （土撥鼠）
meow at liswu.me
https://liswu.me

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-nginx-maintainers/attachments/20210319/ea66bf2a/attachment.htm>