From e377820b6cc482bae6c4288e9020606572cd92a8 Mon Sep 17 00:00:00 2001 From: Valentin Bartenev Date: Thu, 16 Apr 2020 17:49:09 +0300 Subject: [PATCH] Added version 1.17.0 CHANGES. --- CHANGES | 27 +++++++++++++++ docs/changes.xml | 86 ++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 113 insertions(+) diff --git a/CHANGES b/CHANGES index c44466e6..3ffd06b7 100644 --- a/CHANGES +++ b/CHANGES @@ -1,4 +1,31 @@ +Changes with Unit 1.17.0 16 Apr 2020 + + *) Feature: a "return" action with optional "location" for immediate + responses and external redirection. + + *) Feature: fractional weights support for upstream servers. + + *) Bugfix: accidental 502 "Bad Gateway" errors might have occurred in + applications under high load. + + *) Bugfix: memory leak in the router; the bug had appeared in 1.13.0. + + *) Bugfix: segmentation fault might have occurred in the router process + when reaching open connections limit. + + *) Bugfix: "close() failed (9: Bad file descriptor)" alerts might have + appeared in the log while processing large request bodies; the bug + had appeared in 1.16.0. + + *) Bugfix: existing application processes didn't reopen the log file. + + *) Bugfix: incompatibility with some Node.js applications. + + *) Bugfix: broken build on DragonFly BSD; the bug had appeared in + 1.16.0. + + Changes with Unit 1.16.0 12 Mar 2020 *) Feature: basic load-balancing support with round-robin. diff --git a/docs/changes.xml b/docs/changes.xml index 270b49d3..a883ccbb 100644 --- a/docs/changes.xml +++ b/docs/changes.xml @@ -5,6 +5,92 @@ + + + + +NGINX Unit updated to 1.17.0. + + + + + + + + + + +a "return" action with optional "location" for immediate responses and external +redirection. + + + + + +fractional weights support for upstream servers. + + + + + +accidental 502 "Bad Gateway" errors might have occurred in applications under +high load. + + + + + +memory leak in the router; the bug had appeared in 1.13.0. + + + + + +segmentation fault might have occurred in the router process when reaching +open connections limit. + + + + + +"close() failed (9: Bad file descriptor)" alerts might have appeared in the log +while processing large request bodies; the bug had appeared in 1.16.0. + + + + + +existing application processes didn't reopen the log file. + + + + + +incompatibility with some Node.js applications. + + + + + +broken build on DragonFly BSD; the bug had appeared in 1.16.0. + + + + + +