Skip to content

Instantly share code, notes, and snippets.

@parasyte
Created June 4, 2019 18:37
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save parasyte/de596f67a047a097242e14a17f7d3caa to your computer and use it in GitHub Desktop.
Save parasyte/de596f67a047a097242e14a17f7d3caa to your computer and use it in GitHub Desktop.
Nginx bug fixes 1.11.2 ~ 1.6.0

1.11.3 (26 Jul 2016)

*) Bugfix: socket leak when using HTTP/2.

1.11.5 (11 Oct 2016)

*) Bugfix: in the $realip_remote_addr variable.

1.11.6 (15 Nov 2016)

*) Bugfix: graceful shutdown of old worker processes might require infinite time when using HTTP/2.

1.11.7 (13 Dec 2016)

*) Bugfix: when using HTTP/2 and the "limit_req" or "auth_request" directives client request body might be corrupted; the bug had appeared in 1.11.0.

1.11.13 (04 Apr 2017)

*) Bugfix: in the ngx_http_v2_module. Thanks to Piotr Sikora.

*) Bugfix: a segmentation fault might occur in a worker process when using HTTP/2.


1.12.2 (17 Oct 2017)

*) Bugfix: when using HTTP/2 client request body might be corrupted.


1.13.2 (27 Jun 2017)

*) Bugfix: in the ngx_http_v2_module. Thanks to Piotr Sikora.

1.13.6 (10 Oct 2017)

*) Bugfix: in the ngx_http_v2_module. Thanks to Piotr Sikora.

*) Bugfix: when using HTTP/2 nginx might return the 400 response without logging the reason.

*) Bugfix: cache control headers were ignored when caching errors intercepted by error_page.

*) Bugfix: when using HTTP/2 client request body might be corrupted.

1.13.9 (20 Feb 2018)

*) Bugfix: in the ngx_http_v2_module.


1.15.0 (05 Jun 2018)

*) Bugfix: request processing rate might exceed configured rate when using the "limit_req" directive.

1.15.3 (28 Aug 2018)

*) Workaround: some clients might not work when using HTTP/2; the bug had appeared in 1.13.5.

1.15.4 (25 Sep 2018)

*) Bugfix: the "return" directive did not change the response code when returning errors if the request was redirected by the "error_page" directive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment