diff --git a/CHANGES b/CHANGES index 5398910e..79761847 100644 --- a/CHANGES +++ b/CHANGES @@ -1,4 +1,35 @@ +Changes with Unit 1.9.0 30 May 2019 + + *) Feature: request routing by arguments, headers, and cookies. + + *) Feature: route matching patterns allow a wildcard in the middle. + + *) Feature: POST operation for appending elements to arrays in + configuration. + + *) Feature: support for changing credentials using CAP_SETUID and + CAP_SETGID capabilities on Linux without running main process as + privileged user. + + *) Bugfix: memory leak in the router process might have happened when a + client prematurely closed the connection. + + *) Bugfix: applying a large configuration might have failed. + + *) Bugfix: PUT and DELETE operations on array elements in configuration + did not work. + + *) Bugfix: request schema in applications did not reflect TLS + connections. + + *) Bugfix: restored compatibility with Node.js applications that use + ServerResponse._implicitHeader() function; the bug had appeared in + 1.7. + + *) Bugfix: various compatibility issues with Node.js applications. + + Changes with Unit 1.8.0 01 Mar 2019 *) Change: now three numbers are always used for versioning: major, diff --git a/docs/changes.xml b/docs/changes.xml index e4b8158d..e1a8734c 100644 --- a/docs/changes.xml +++ b/docs/changes.xml @@ -5,6 +5,109 @@ + + + + +Initial release of Go 1.11 module for NGINX Unit. + + + + + + + + + + +NGINX Unit updated to 1.9.0. + + + + + + + + + + +request routing by arguments, headers, and cookies. + + + + + +route matching patterns allow a wildcard in the middle. + + + + + +POST operation for appending elements to arrays in configuration. + + + + + +support for changing credentials using CAP_SETUID and CAP_SETGID capabilities +on Linux without running main process as privileged user. + + + + + +memory leak in the router process might have happened when a client +prematurely closed the connection. + + + + + +applying a large configuration might have failed. + + + + + +PUT and DELETE operations on array elements in configuration did not work. + + + + + +request schema in applications did not reflect TLS connections. + + + + + +restored compatibility with Node.js applications that use +ServerResponse._implicitHeader() function; the bug had appeared in 1.7. + + + + + +various compatibility issues with Node.js applications. + + + + + +