phpged/unit
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity
unit/docs/changes.xml

3584 lines
74 KiB
XML
Raw Normal View History

Added changelogs generation tools.
2017-10-19 14:48:58 +00:00
<?xml version="1.0" ?>
<!DOCTYPE change_log SYSTEM "changes.dtd" >
<change_log title="unit">
Version bump.
2022-12-16 12:42:53 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8 unit-python3.9 unit-python3.10 unit-python3.11
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11 unit-jsc13
unit-jsc14 unit-jsc15 unit-jsc16 unit-jsc17 unit-jsc18
unit-jsc19"
ver="1.30.0" rev="1"
date="" time=""
packager="Nginx Packaging &lt;nginx-packaging@f5.com&gt;">
<change>
<para>
NGINX Unit updated to 1.30.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.30.0" rev="1"
date="" time=""
packager="Nginx Packaging &lt;nginx-packaging@f5.com&gt;">
</changes>
Version bump.
2022-09-19 10:59:59 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
Docs: added changelog for Python 3.11. While at it, fixed changelogs generation for Python 3.10 as well.
2022-12-15 16:37:52 +00:00
unit-python3.8 unit-python3.9 unit-python3.10 unit-python3.11
Version bump.
2022-09-19 10:59:59 +00:00
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11 unit-jsc13
Packages: added Ubuntu 22.10 "kinetic" support.
2022-11-16 13:05:57 +00:00
unit-jsc14 unit-jsc15 unit-jsc16 unit-jsc17 unit-jsc18
unit-jsc19"
Version bump.
2022-09-19 10:59:59 +00:00
ver="1.29.0" rev="1"
Added version 1.29.0 CHANGES.
2022-12-15 12:32:46 +00:00
date="2022-12-15" time="18:00:00 +0300"
Version bump.
2022-09-19 10:59:59 +00:00
packager="Nginx Packaging &lt;nginx-packaging@f5.com&gt;">
<change>
<para>
NGINX Unit updated to 1.29.0.
</para>
</change>
</changes>
Packages: added Ubuntu 22.10 "kinetic" support.
2022-11-16 13:05:57 +00:00
<changes apply="unit-jsc19" ver="1.29.0" rev="1"
date="2022-11-18" time="15:00:00 +0400"
packager="Nginx Packaging &lt;nginx-packaging@f5.com&gt;">
<change>
<para>
Initial release of Java 19 module for NGINX Unit.
</para>
</change>
</changes>
Docs: added changelog for Python 3.11. While at it, fixed changelogs generation for Python 3.10 as well.
2022-12-15 16:37:52 +00:00
<changes apply="unit-python3.11" ver="1.29.0" rev="1"
date="2022-12-15" time="08:00:00 -0800"
packager="Nginx Packaging &lt;nginx-packaging@f5.com&gt;">
<change>
<para>
Initial release of Python 3.11 module for NGINX Unit.
</para>
</change>
</changes>
Version bump.
2022-09-19 10:59:59 +00:00
<changes apply="unit" ver="1.29.0" rev="1"
Added version 1.29.0 CHANGES.
2022-12-15 12:32:46 +00:00
date="2022-12-15" time="18:00:00 +0300"
Version bump.
2022-09-19 10:59:59 +00:00
packager="Nginx Packaging &lt;nginx-packaging@f5.com&gt;">
Configuration: stopped automatic migration to the "share" behavior. This commit removed the $uri auto-append for the "share" option introduced in rev be6409cdb028. The main reason is that it causes problems when preparing Unit configurations to be loaded at startup from the state directory. E.g. Docker. A valid conf.json file with $uri references will end up with $uri$uri due to the auto-append.
2022-10-14 06:00:02 +00:00
<change type="change">
<para>
removed $uri auto-append for "share" when loading configuration.
</para>
</change>
Preferring system crypto policy. If we don't call SSL_CTX_set_cipher_list(), then it uses the system's default. Link: <https://fedoraproject.org/wiki/Changes/CryptoPolicy> Link: <https://docs.fedoraproject.org/en-US/packaging-guidelines/CryptoPolicies/> Link: <https://www.redhat.com/en/blog/consistent-security-crypto-policies-red-hat-enterprise-linux-8> Signed-off-by: Remi Collet <remi@remirepo.net> Acked-by: Andrei Belov <defan@nginx.com> [ alx: add changelog and tweak commit message ] Signed-off-by: Alejandro Colomar <alx@nginx.com>
2019-01-16 07:38:53 +00:00
<change type="change">
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
prefer system crypto policy instead of hardcoding a default.
Preferring system crypto policy. If we don't call SSL_CTX_set_cipher_list(), then it uses the system's default. Link: <https://fedoraproject.org/wiki/Changes/CryptoPolicy> Link: <https://docs.fedoraproject.org/en-US/packaging-guidelines/CryptoPolicies/> Link: <https://www.redhat.com/en/blog/consistent-security-crypto-policies-red-hat-enterprise-linux-8> Signed-off-by: Remi Collet <remi@remirepo.net> Acked-by: Andrei Belov <defan@nginx.com> [ alx: add changelog and tweak commit message ] Signed-off-by: Alejandro Colomar <alx@nginx.com>
2019-01-16 07:38:53 +00:00
</para>
</change>
Isolation: wired up cgroup support to the config system. This hooks the cgroup support up to the config system so it can actually be used. To make use of this in unit a new "cgroup" section has been added to the isolation configuration. e.g "applications": { "python": { "type": "python", "processes": 5, "path": "/opt/unit/unit-cgroup-test/", "module": "app", "isolation": { "cgroup": { "path": "app/python" } } } } Now there are two ways to specify the path, relative, like the above (without a leading '/') and absolute (with a leading '/'). In the above case the "python" application is placed into its own cgroup under CGROUP_ROOT/<main unit process cgroup>/app/python. Whereas if you specified say "path": "/unit/app/python" Then the python application would be placed under CGROUP_ROOT/unit/app/python The first option allows you to easily take advantage of any resource limits that have already been configured for unit. With the second method (absolute pathname) if you know of an already existing cgroup where you'd like to place it, you can, e.g "path": "/system.slice/unit/python" Where system.slice has already been created by systemd and may already have some overall system limits applied which would also apply to unit. Limits apply down the hierarchy and lower groups can't exceed the previous group limits. So what does this actually look like? Lets take the unit-calculator application[0] and have each of its applications placed into their own cgroup. If we give each application a new section like "isolation": { "cgroup": { "path": "/unit/unit-calculator/add" } } changing the path for each one, we can visualise the result with the systemd-cgls command, e.g │ └─session-5.scope (#4561) │ ├─ 6667 sshd: andrew [priv] │ ├─ 6684 sshd: andrew@pts/0 │ ├─ 6685 -bash │ ├─ 12632 unit: main v1.28.0 [/opt/unit/sbin/unitd --control 127.0.0.1:808> │ ├─ 12634 unit: controller │ ├─ 12635 unit: router │ ├─ 13550 systemd-cgls │ └─ 13551 less ├─unit (#4759) │ └─unit-calculator (#5037) │ ├─subtract (#5069) │ │ ├─ 12650 unit: "subtract" prototype │ │ └─ 12651 unit: "subtract" application │ ├─multiply (#5085) │ │ ├─ 12653 unit: "multiply" prototype │ │ └─ 12654 unit: "multiply" application │ ├─divide (#5101) │ │ ├─ 12671 unit: "divide" prototype │ │ └─ 12672 node divide.js │ ├─sqroot (#5117) │ │ ├─ 12679 unit: "sqroot" prototype │ │ └─ 12680 /home/andrew/src/unit-calculator/sqroot/sqroot │ └─add (#5053) │ ├─ 12648 unit: "add" prototype │ └─ 12649 unit: "add" application We used an absolute path so the cgroups will be created relative to the main cgroupfs mount, e.g /sys/fs/cgroup We can see that the main unit processes are in the same cgroup as the shell from where they were started, by default child process are placed into the same cgroup as the parent. Then we can see that each application has been placed into its own cgroup under /sys/fs/cgroup Taking another example of a simple 5 process python application, with "isolation": { "cgroup": { "path": "app/python" } } Here we have specified a relative path and thus the python application will be placed below the existing cgroup that contains the main unit process. E.g │ │ │ ├─app-glib-cinnamon\x2dcustom\x2dlauncher\x2d3-43951.scope (#90951) │ │ │ │ ├─ 988 unit: main v1.28.0 [/opt/unit/sbin/unitd --no-daemon] │ │ │ │ ├─ 990 unit: controller │ │ │ │ ├─ 991 unit: router │ │ │ │ ├─ 43951 xterm -bg rgb:20/20/20 -fg white -fa DejaVu Sans Mono │ │ │ │ ├─ 43956 bash │ │ │ │ ├─ 58828 sudo -i │ │ │ │ ├─ 58831 -bash │ │ │ │ └─app (#107351) │ │ │ │ └─python (#107367) │ │ │ │ ├─ 992 unit: "python" prototype │ │ │ │ ├─ 993 unit: "python" application │ │ │ │ ├─ 994 unit: "python" application │ │ │ │ ├─ 995 unit: "python" application │ │ │ │ ├─ 996 unit: "python" application │ │ │ │ └─ 997 unit: "python" application [0]: <https://github.com/lcrilly/unit-calculator> Reviewed-by: Alejandro Colomar <alx@nginx.com> Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
2022-10-24 16:14:06 +00:00
<change type="feature">
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
njs support with the basic syntax of JS template literals.
Isolation: wired up cgroup support to the config system. This hooks the cgroup support up to the config system so it can actually be used. To make use of this in unit a new "cgroup" section has been added to the isolation configuration. e.g "applications": { "python": { "type": "python", "processes": 5, "path": "/opt/unit/unit-cgroup-test/", "module": "app", "isolation": { "cgroup": { "path": "app/python" } } } } Now there are two ways to specify the path, relative, like the above (without a leading '/') and absolute (with a leading '/'). In the above case the "python" application is placed into its own cgroup under CGROUP_ROOT/<main unit process cgroup>/app/python. Whereas if you specified say "path": "/unit/app/python" Then the python application would be placed under CGROUP_ROOT/unit/app/python The first option allows you to easily take advantage of any resource limits that have already been configured for unit. With the second method (absolute pathname) if you know of an already existing cgroup where you'd like to place it, you can, e.g "path": "/system.slice/unit/python" Where system.slice has already been created by systemd and may already have some overall system limits applied which would also apply to unit. Limits apply down the hierarchy and lower groups can't exceed the previous group limits. So what does this actually look like? Lets take the unit-calculator application[0] and have each of its applications placed into their own cgroup. If we give each application a new section like "isolation": { "cgroup": { "path": "/unit/unit-calculator/add" } } changing the path for each one, we can visualise the result with the systemd-cgls command, e.g │ └─session-5.scope (#4561) │ ├─ 6667 sshd: andrew [priv] │ ├─ 6684 sshd: andrew@pts/0 │ ├─ 6685 -bash │ ├─ 12632 unit: main v1.28.0 [/opt/unit/sbin/unitd --control 127.0.0.1:808> │ ├─ 12634 unit: controller │ ├─ 12635 unit: router │ ├─ 13550 systemd-cgls │ └─ 13551 less ├─unit (#4759) │ └─unit-calculator (#5037) │ ├─subtract (#5069) │ │ ├─ 12650 unit: "subtract" prototype │ │ └─ 12651 unit: "subtract" application │ ├─multiply (#5085) │ │ ├─ 12653 unit: "multiply" prototype │ │ └─ 12654 unit: "multiply" application │ ├─divide (#5101) │ │ ├─ 12671 unit: "divide" prototype │ │ └─ 12672 node divide.js │ ├─sqroot (#5117) │ │ ├─ 12679 unit: "sqroot" prototype │ │ └─ 12680 /home/andrew/src/unit-calculator/sqroot/sqroot │ └─add (#5053) │ ├─ 12648 unit: "add" prototype │ └─ 12649 unit: "add" application We used an absolute path so the cgroups will be created relative to the main cgroupfs mount, e.g /sys/fs/cgroup We can see that the main unit processes are in the same cgroup as the shell from where they were started, by default child process are placed into the same cgroup as the parent. Then we can see that each application has been placed into its own cgroup under /sys/fs/cgroup Taking another example of a simple 5 process python application, with "isolation": { "cgroup": { "path": "app/python" } } Here we have specified a relative path and thus the python application will be placed below the existing cgroup that contains the main unit process. E.g │ │ │ ├─app-glib-cinnamon\x2dcustom\x2dlauncher\x2d3-43951.scope (#90951) │ │ │ │ ├─ 988 unit: main v1.28.0 [/opt/unit/sbin/unitd --no-daemon] │ │ │ │ ├─ 990 unit: controller │ │ │ │ ├─ 991 unit: router │ │ │ │ ├─ 43951 xterm -bg rgb:20/20/20 -fg white -fa DejaVu Sans Mono │ │ │ │ ├─ 43956 bash │ │ │ │ ├─ 58828 sudo -i │ │ │ │ ├─ 58831 -bash │ │ │ │ └─app (#107351) │ │ │ │ └─python (#107367) │ │ │ │ ├─ 992 unit: "python" prototype │ │ │ │ ├─ 993 unit: "python" application │ │ │ │ ├─ 994 unit: "python" application │ │ │ │ ├─ 995 unit: "python" application │ │ │ │ ├─ 996 unit: "python" application │ │ │ │ └─ 997 unit: "python" application [0]: <https://github.com/lcrilly/unit-calculator> Reviewed-by: Alejandro Colomar <alx@nginx.com> Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
2022-10-24 16:14:06 +00:00
</para>
</change>
Python: Added support for Python 3.11. Python 3.8 added a new Python initialisation configuration API[0]. Python 3.11 marked the old API as deprecated resulting in the following compiler warnings which we treat as errors, failing the build src/python/nxt_python.c: In function ‘nxt_python_start’: src/python/nxt_python.c:130:13: error: ‘Py_SetProgramName’ is deprecated [-Werror=deprecated-declarations] 130 | Py_SetProgramName(nxt_py_home); | ^~~~~~~~~~~~~~~~~ In file included from /opt/python-3.11/include/python3.11/Python.h:94, from src/python/nxt_python.c:7: /opt/python-3.11/include/python3.11/pylifecycle.h:37:38: note: declared here 37 | Py_DEPRECATED(3.11) PyAPI_FUNC(void) Py_SetProgramName(const wchar_t *); | ^~~~~~~~~~~~~~~~~ src/python/nxt_python.c:134:13: error: ‘Py_SetPythonHome’ is deprecated [-Werror=deprecated-declarations] 134 | Py_SetPythonHome(nxt_py_home); | ^~~~~~~~~~~~~~~~ /opt/python-3.11/include/python3.11/pylifecycle.h:40:38: note: declared here 40 | Py_DEPRECATED(3.11) PyAPI_FUNC(void) Py_SetPythonHome(const wchar_t *); | ^~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors We actually have a few config scenarios: Python < 3, Python >= 3.0 < 3.8 and for Python 3 we have two configs where we select one based on virtual environment setup. Factor out the Python 3 config initialisation into its own function. We actually create two functions, one for Python 3.8+ and one for older Python 3. We pick the right function to use at build time. The new API also has error checking (where the old API doesn't) which we handle. [0]: https://peps.python.org/pep-0587/ Closes: <https://github.com/nginx/unit/issues/710> [ Andrew: Expanded upon patch from @sandeep-gh ] Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
2022-11-17 21:56:58 +00:00
<change type="feature">
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
support per-application cgroups on Linux.
Python: Added support for Python 3.11. Python 3.8 added a new Python initialisation configuration API[0]. Python 3.11 marked the old API as deprecated resulting in the following compiler warnings which we treat as errors, failing the build src/python/nxt_python.c: In function ‘nxt_python_start’: src/python/nxt_python.c:130:13: error: ‘Py_SetProgramName’ is deprecated [-Werror=deprecated-declarations] 130 | Py_SetProgramName(nxt_py_home); | ^~~~~~~~~~~~~~~~~ In file included from /opt/python-3.11/include/python3.11/Python.h:94, from src/python/nxt_python.c:7: /opt/python-3.11/include/python3.11/pylifecycle.h:37:38: note: declared here 37 | Py_DEPRECATED(3.11) PyAPI_FUNC(void) Py_SetProgramName(const wchar_t *); | ^~~~~~~~~~~~~~~~~ src/python/nxt_python.c:134:13: error: ‘Py_SetPythonHome’ is deprecated [-Werror=deprecated-declarations] 134 | Py_SetPythonHome(nxt_py_home); | ^~~~~~~~~~~~~~~~ /opt/python-3.11/include/python3.11/pylifecycle.h:40:38: note: declared here 40 | Py_DEPRECATED(3.11) PyAPI_FUNC(void) Py_SetPythonHome(const wchar_t *); | ^~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors We actually have a few config scenarios: Python < 3, Python >= 3.0 < 3.8 and for Python 3 we have two configs where we select one based on virtual environment setup. Factor out the Python 3 config initialisation into its own function. We actually create two functions, one for Python 3.8+ and one for older Python 3. We pick the right function to use at build time. The new API also has error checking (where the old API doesn't) which we handle. [0]: https://peps.python.org/pep-0587/ Closes: <https://github.com/nginx/unit/issues/710> [ Andrew: Expanded upon patch from @sandeep-gh ] Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
2022-11-17 21:56:58 +00:00
</para>
</change>
Basic njs support.
2022-11-20 15:16:51 +00:00
<change type="feature">
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
the $request_time variable contains the request processing time.
Basic njs support.
2022-11-20 15:16:51 +00:00
</para>
</change>
TLS: Using ERR_get_error_all() with OpenSSL 3. Link: <https://www.openssl.org/docs/man3.0/man7/migration_guide.html> Cc: Andy Postnikov <apostnikov@gmail.com> Cc: Andrew Clayton <a.clayton@nginx.com> Signed-off-by: Remi Collet <remi@remirepo.net> Signed-off-by: Alejandro Colomar <alx@nginx.com>
2021-11-18 16:47:39 +00:00
<change type="feature">
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
"prefix" option in Python applications to set WSGI "SCRIPT_NAME"
and ASGI root-path variables.
TLS: Using ERR_get_error_all() with OpenSSL 3. Link: <https://www.openssl.org/docs/man3.0/man7/migration_guide.html> Cc: Andy Postnikov <apostnikov@gmail.com> Cc: Andrew Clayton <a.clayton@nginx.com> Signed-off-by: Remi Collet <remi@remirepo.net> Signed-off-by: Alejandro Colomar <alx@nginx.com>
2021-11-18 16:47:39 +00:00
</para>
</change>
PHP: Fixed php_module_startup() call for PHP 8.2. PHP 8.2 changed the prototype of the function, removing the last parameter. Signed-off-by: Remi Collet <remi@remirepo.net> Cc: Timo Stark <t.stark@nginx.com> Cc: George Peter Banyard <girgias@php.net> Tested-by: Andy Postnikov <apostnikov@gmail.com> Acked-by: Andy Postnikov <apostnikov@gmail.com> Reviewed-by: Andrew Clayton <a.clayton@nginx.com> Signed-off-by: Alejandro Colomar <alx@nginx.com>
2022-06-02 14:16:35 +00:00
<change type="feature">
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
compatibility with Python 3.11.
PHP: Fixed php_module_startup() call for PHP 8.2. PHP 8.2 changed the prototype of the function, removing the last parameter. Signed-off-by: Remi Collet <remi@remirepo.net> Cc: Timo Stark <t.stark@nginx.com> Cc: George Peter Banyard <girgias@php.net> Tested-by: Andy Postnikov <apostnikov@gmail.com> Acked-by: Andy Postnikov <apostnikov@gmail.com> Reviewed-by: Andrew Clayton <a.clayton@nginx.com> Signed-off-by: Alejandro Colomar <alx@nginx.com>
2022-06-02 14:16:35 +00:00
</para>
</change>
Node.js: added "shortCircuit" option for ES modules hook. Starting from Node.js v18.6.0 return value from all hooks must have "shortCircuit: true" option specified. For more information see: https://github.com/nodejs/node/commit/10bcad5c6e
2022-12-06 14:30:13 +00:00
<change type="feature">
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
compatibility with OpenSSL 3.
Node.js: added "shortCircuit" option for ES modules hook. Starting from Node.js v18.6.0 return value from all hooks must have "shortCircuit: true" option specified. For more information see: https://github.com/nodejs/node/commit/10bcad5c6e
2022-12-06 14:30:13 +00:00
</para>
</change>
Ruby: added support for rack V3. Ruby applications would fail to start if they were using rack v3 2022/09/28 15:48:46 [alert] 0#80912 [unit] Ruby: Failed to parse rack script 2022/09/28 15:48:46 [notice] 80911#80911 app process 80912 exited with code 1 This was due to a change in the rack API Rack V2 def self.load_file(path, opts = Server::Options.new) ... cfgfile.sub!(/^__END__\n.*\Z/m, '') app = new_from_string cfgfile, path return app, options end Rack V3 def self.load_file(path) ... return new_from_string(config, path) end This patch handles _both_ the above APIs by correctly handling the cases where we do and don't get an array returned from nxt_ruby_rack_parse_script(). Closes: <https://github.com/nginx/unit/issues/755> Tested-by: Andrew Clayton <a.clayton@nginx.com> Reviewed-by: Andrew Clayton <a.clayton@nginx.com> [ Andrew: Patch by Zhidao, commit message by me with input from Zhidao ] Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
2022-09-28 14:51:55 +00:00
<change type="feature">
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
compatibility with PHP 8.2.
Ruby: added support for rack V3. Ruby applications would fail to start if they were using rack v3 2022/09/28 15:48:46 [alert] 0#80912 [unit] Ruby: Failed to parse rack script 2022/09/28 15:48:46 [notice] 80911#80911 app process 80912 exited with code 1 This was due to a change in the rack API Rack V2 def self.load_file(path, opts = Server::Options.new) ... cfgfile.sub!(/^__END__\n.*\Z/m, '') app = new_from_string cfgfile, path return app, options end Rack V3 def self.load_file(path) ... return new_from_string(config, path) end This patch handles _both_ the above APIs by correctly handling the cases where we do and don't get an array returned from nxt_ruby_rack_parse_script(). Closes: <https://github.com/nginx/unit/issues/755> Tested-by: Andrew Clayton <a.clayton@nginx.com> Reviewed-by: Andrew Clayton <a.clayton@nginx.com> [ Andrew: Patch by Zhidao, commit message by me with input from Zhidao ] Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
2022-09-28 14:51:55 +00:00
</para>
</change>
HTTP: added a $request_time variable.
2022-10-12 00:21:02 +00:00
<change type="feature">
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
compatibility with Node.js 19.0.
HTTP: added a $request_time variable.
2022-10-12 00:21:02 +00:00
</para>
</change>
Configuration: added the regex status in configure summary.
2022-10-20 04:02:27 +00:00
<change type="feature">
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
Ruby Rack v3 support.
Configuration: added the regex status in configure summary.
2022-10-20 04:02:27 +00:00
</para>
</change>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
<change type="bugfix">
Python: Added "prefix" to configuration. This patch gives users the option to set a `"prefix"` attribute for Python applications, either at the top level or for specific `"target"`s. If the attribute is present, the value of `"prefix"` must be a string beginning with `"/"`. If the value of the `"prefix"` attribute is longer than 1 character and ends in `"/"`, the trailing `"/"` is stripped. The purpose of the `"prefix"` attribute is to set the `SCRIPT_NAME` context value for WSGI applications and the `root_path` context value for ASGI applications, allowing applications to properly route requests regardless of the path that the server uses to expose the application. The context value is only set if the request's URL path begins with the value of the `"prefix"` attribute. In all other cases, the `SCRIPT_NAME` or `root_path` values are not set. In addition, for WSGI applications, the value of `"prefix"` will be stripped from the beginning of the request's URL path before it is sent to the application. Reviewed-by: Andrei Zeliankou <zelenkov@nginx.com> Reviewed-by: Artem Konev <artem.konev@nginx.com> Signed-off-by: Alejandro Colomar <alx@nginx.com>
2021-11-14 15:47:07 +00:00
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
fix error in connection statistics when using proxy.
Python: Added "prefix" to configuration. This patch gives users the option to set a `"prefix"` attribute for Python applications, either at the top level or for specific `"target"`s. If the attribute is present, the value of `"prefix"` must be a string beginning with `"/"`. If the value of the `"prefix"` attribute is longer than 1 character and ends in `"/"`, the trailing `"/"` is stripped. The purpose of the `"prefix"` attribute is to set the `SCRIPT_NAME` context value for WSGI applications and the `root_path` context value for ASGI applications, allowing applications to properly route requests regardless of the path that the server uses to expose the application. The context value is only set if the request's URL path begins with the value of the `"prefix"` attribute. In all other cases, the `SCRIPT_NAME` or `root_path` values are not set. In addition, for WSGI applications, the value of `"prefix"` will be stripped from the beginning of the request's URL path before it is sent to the application. Reviewed-by: Andrei Zeliankou <zelenkov@nginx.com> Reviewed-by: Artem Konev <artem.konev@nginx.com> Signed-off-by: Alejandro Colomar <alx@nginx.com>
2021-11-14 15:47:07 +00:00
</para>
</change>
HTTP: fixed cookie parsing. The fixing supports the cookie value with the '=' character. This is related to #756 PR on Github. Thanks to changxiaocui.
2022-09-18 18:45:44 +00:00
<change type="bugfix">
<para>
fix HTTP cookie parsing when the value contains an equals sign.
</para>
</change>
Status: fixed error in connection statistics. When proxy is used, the number of accepted connections is not counted, This also results in the wrong number of active connections.
2022-09-21 17:01:18 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
PHP directory URLs without a trailing '/' would give a 503 error (fixed with
a 301 re-direct).
Status: fixed error in connection statistics. When proxy is used, the number of accepted connections is not counted, This also results in the wrong number of active connections.
2022-09-21 17:01:18 +00:00
</para>
</change>
PHP: allowed to specify URLs without a trailing '/'. Both @lucatacconi & @mwoodpatrick reported what appears to be the same issue on GitHub. Namely that when using the PHP language module and trying to access a URL that is a directory but without specifying the trailing '/', they were getting a '503 Service Unavailable' error. Note: This is when _not_ using the 'script' option. E.g with the following config { "listeners": { "[::1]:8080": { "pass": "applications/php" } }, "applications": { "php": { "type": "php", "root": "/var/tmp/unit-php" } } } and with a directory path of /var/tmp/unit-php/foo containing an index.php, you would see the following $ curl http://localhost/foo <title>Error 503</title> Error 503 However $ curl http://localhost/foo/ would work and serve up the index.php This commit fixes the above so you get the desired behaviour without specifying the trailing '/' by doing the following 1] If the URL doesn't end in .php and doesn't have a trailing '/' then check if the requested path is a directory. 2) If it is a directory then create a 301 re-direct pointing to it. This matches the behaviour of the likes of nginx, Apache and lighttpd. This also matches the behaviour of the "share" action in Unit. This doesn't effect the behaviour of the 'script' option which bypasses the nxt_php_dynamic_request() function. This also adds a couple of tests to test/test_php_application.py to ensure this continues to work. Closes: <https://github.com/nginx/unit/issues/717> Closes: <https://github.com/nginx/unit/issues/753> Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
2022-09-16 13:38:53 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
missing error checks in the C API.
</para>
</change>
<change type="bugfix">
<para>
report the regex status in configure summary.
PHP: allowed to specify URLs without a trailing '/'. Both @lucatacconi & @mwoodpatrick reported what appears to be the same issue on GitHub. Namely that when using the PHP language module and trying to access a URL that is a directory but without specifying the trailing '/', they were getting a '503 Service Unavailable' error. Note: This is when _not_ using the 'script' option. E.g with the following config { "listeners": { "[::1]:8080": { "pass": "applications/php" } }, "applications": { "php": { "type": "php", "root": "/var/tmp/unit-php" } } } and with a directory path of /var/tmp/unit-php/foo containing an index.php, you would see the following $ curl http://localhost/foo <title>Error 503</title> Error 503 However $ curl http://localhost/foo/ would work and serve up the index.php This commit fixes the above so you get the desired behaviour without specifying the trailing '/' by doing the following 1] If the URL doesn't end in .php and doesn't have a trailing '/' then check if the requested path is a directory. 2) If it is a directory then create a 301 re-direct pointing to it. This matches the behaviour of the likes of nginx, Apache and lighttpd. This also matches the behaviour of the "share" action in Unit. This doesn't effect the behaviour of the 'script' option which bypasses the nxt_php_dynamic_request() function. This also adds a couple of tests to test/test_php_application.py to ensure this continues to work. Closes: <https://github.com/nginx/unit/issues/717> Closes: <https://github.com/nginx/unit/issues/753> Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
2022-09-16 13:38:53 +00:00
</para>
</change>
Version bump.
2022-09-19 10:59:59 +00:00
</changes>
Version bump.
2022-06-17 08:46:30 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8 unit-python3.9 unit-python3.10
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11 unit-jsc13
unit-jsc14 unit-jsc15 unit-jsc16 unit-jsc17 unit-jsc18"
ver="1.28.0" rev="1"
Added version 1.28.0 CHANGES.
2022-09-13 08:27:13 +00:00
date="2022-09-13" time="18:00:00 +0300"
Switched changelogs to packaging alias instead of personal emails.
2022-06-20 14:21:43 +00:00
packager="Nginx Packaging &lt;nginx-packaging@f5.com&gt;">
Version bump.
2022-06-17 08:46:30 +00:00
<change>
<para>
NGINX Unit updated to 1.28.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.28.0" rev="1"
Added version 1.28.0 CHANGES.
2022-09-13 08:27:13 +00:00
date="2022-09-13" time="18:00:00 +0300"
Switched changelogs to packaging alias instead of personal emails.
2022-06-20 14:21:43 +00:00
packager="Nginx Packaging &lt;nginx-packaging@f5.com&gt;">
Version bump.
2022-06-17 08:46:30 +00:00
Put changes entry in the correct position.
2022-08-05 10:47:17 +00:00
<change type="change">
<para>
increased the applications' startup timeout.
</para>
</change>
Disallowed abstract unix socket syntax in non-Linux systems. The previous commit added/fixed support for abstract Unix domain sockets on Linux with a leading '@' or '\0'. To be consistent in all platforms, treat those prefixes as markers for abstract sockets in all platforms, and fail if abstract sockets are not supported by the platform. That will avoid mistakes when copying a config file from a Linux system and using it in non-Linux, which would surprisingly create a normal socket.
2022-07-28 14:10:32 +00:00
<change type="change">
<para>
disallowed abstract Unix domain socket syntax in non-Linux systems.
</para>
</change>
Fixed support for abstract Unix sockets. Unix domain sockets are normally backed by files in the filesystem. This has historically been problematic when closing and opening again such sockets, since SO_REUSEADDR is ignored for Unix sockets (POSIX left the behavior of SO_REUSEADDR as implementation-defined, and most --if not all-- implementations decided to just ignore this flag). Many solutions are available for this problem, but all of them have important caveats: - unlink(2) the file when it's not needed anymore. This is not easy, because the process that controls the fd may not be the same process that created the file, and may not have file permissions to remove it. Further solutions can be applied to that caveat: - unlink(2) the file right after creation. This will remove the pathname from the filesystem without closing the socket (it will continue to live until the last fd is closed). This is not useful for us, since we need the pathname of the socket as its interface. - chown(2) or chmod(2) the directory that contains the socket. For removing a file from the filesystem, a process needs write permissions in the containing directory. We could put sockets in dummy directories that can be chown(2)ed to nobody. This could be dangerous, though, as we don't control the socket names. It is our users who configure the socket name in their configuration, and so it's easy that they don't understand the many implications of not chosing an appropriate socket pathname. A user could unknowingly put the socket in a directory that is not supposed to be owned by user nobody, and if we blindly chown(2) or chmod(2) the directory, we could be creating a big security hole. - Ask the main process to remove the socket. This would require a very complex communication mechanism with the main process, which is not impossible, but let's avoid it if there are simpler solutions. - Give the child process the CAP_DAC_OVERRIDE capability. That is one of the most powerful capabilities. A process with that capability can be considered root for most practical aspects. Even if the capability is disabled for most of the lifetime of the process, there's a slight chance that a malicious actor could activate it and then easily do serious damage to the system. - unlink(2) the file right before calling bind(2). This is dangerous because another process (for example, another running instance of unitd(8)), could be using the socket, and removing the pathname from the filesystem would be problematic. To do this correctly, a lot of checks should be added before the actual unlink(2), which is error-prone, and difficult to do correctly, and atomically. - Use abstract-namespace Unix domain sockets. This is the simplest solution, as it only requires accepting a slightly different syntax (basically a @ prefix) for the socket name, to transform it into a string starting with a null byte ('\0') that the kernel can understand. The patch is minimal. Since abstract sockets live in an abstract namespace, they don't create files in the filesystem, so there's no need to remove them later. The kernel removes the name when the last fd to it has been closed. One caveat is that only Linux currently supports this kind of Unix sockets. Of course, a solution to that could be to ask other kernels to implement such a feature. Another caveat is that filesystem permissions can't be used to control access to the socket file (since, of course, there's no file). Anyone knowing the socket name can access to it. The only method to control access to it is by using network_namespaces(7). Since in unitd(8) we're using 0666 file sockets, abstract sockets should be no more insecure than that (anyone can already read/write to the listener sockets). - Ask the kernel to implement a simpler way to unlink(2) socket files when they are not needed anymore. I've suggested that to the <linux-fsdevel@vger.kernel.org> mailing list, in: <lore.kernel.org/linux-fsdevel/0bc5f919-bcfd-8fd0-a16b-9f060088158a@gmail.com/T> In this commit, I decided to go for the easiest/simplest solution, which is abstract sockets. In fact, we already had partial support. This commit only fixes some small bug in the existing code so that abstract Unix sockets work: - Don't chmod(2) the socket if it's an abstract one. This fixes the creation of abstract sockets, but doesn't make them usable, since we produce them with a trailing '\0' in their name. That will be fixed in the following commit. This closes #669 issue on GitHub.
2022-07-28 14:10:32 +00:00
<change type="feature">
<para>
Reordered changes for 1.28.0 by significance (subjective).
2022-09-13 08:16:55 +00:00
basic statistics API.
Fixed support for abstract Unix sockets. Unix domain sockets are normally backed by files in the filesystem. This has historically been problematic when closing and opening again such sockets, since SO_REUSEADDR is ignored for Unix sockets (POSIX left the behavior of SO_REUSEADDR as implementation-defined, and most --if not all-- implementations decided to just ignore this flag). Many solutions are available for this problem, but all of them have important caveats: - unlink(2) the file when it's not needed anymore. This is not easy, because the process that controls the fd may not be the same process that created the file, and may not have file permissions to remove it. Further solutions can be applied to that caveat: - unlink(2) the file right after creation. This will remove the pathname from the filesystem without closing the socket (it will continue to live until the last fd is closed). This is not useful for us, since we need the pathname of the socket as its interface. - chown(2) or chmod(2) the directory that contains the socket. For removing a file from the filesystem, a process needs write permissions in the containing directory. We could put sockets in dummy directories that can be chown(2)ed to nobody. This could be dangerous, though, as we don't control the socket names. It is our users who configure the socket name in their configuration, and so it's easy that they don't understand the many implications of not chosing an appropriate socket pathname. A user could unknowingly put the socket in a directory that is not supposed to be owned by user nobody, and if we blindly chown(2) or chmod(2) the directory, we could be creating a big security hole. - Ask the main process to remove the socket. This would require a very complex communication mechanism with the main process, which is not impossible, but let's avoid it if there are simpler solutions. - Give the child process the CAP_DAC_OVERRIDE capability. That is one of the most powerful capabilities. A process with that capability can be considered root for most practical aspects. Even if the capability is disabled for most of the lifetime of the process, there's a slight chance that a malicious actor could activate it and then easily do serious damage to the system. - unlink(2) the file right before calling bind(2). This is dangerous because another process (for example, another running instance of unitd(8)), could be using the socket, and removing the pathname from the filesystem would be problematic. To do this correctly, a lot of checks should be added before the actual unlink(2), which is error-prone, and difficult to do correctly, and atomically. - Use abstract-namespace Unix domain sockets. This is the simplest solution, as it only requires accepting a slightly different syntax (basically a @ prefix) for the socket name, to transform it into a string starting with a null byte ('\0') that the kernel can understand. The patch is minimal. Since abstract sockets live in an abstract namespace, they don't create files in the filesystem, so there's no need to remove them later. The kernel removes the name when the last fd to it has been closed. One caveat is that only Linux currently supports this kind of Unix sockets. Of course, a solution to that could be to ask other kernels to implement such a feature. Another caveat is that filesystem permissions can't be used to control access to the socket file (since, of course, there's no file). Anyone knowing the socket name can access to it. The only method to control access to it is by using network_namespaces(7). Since in unitd(8) we're using 0666 file sockets, abstract sockets should be no more insecure than that (anyone can already read/write to the listener sockets). - Ask the kernel to implement a simpler way to unlink(2) socket files when they are not needed anymore. I've suggested that to the <linux-fsdevel@vger.kernel.org> mailing list, in: <lore.kernel.org/linux-fsdevel/0bc5f919-bcfd-8fd0-a16b-9f060088158a@gmail.com/T> In this commit, I decided to go for the easiest/simplest solution, which is abstract sockets. In fact, we already had partial support. This commit only fixes some small bug in the existing code so that abstract Unix sockets work: - Don't chmod(2) the socket if it's an abstract one. This fixes the creation of abstract sockets, but doesn't make them usable, since we produce them with a trailing '\0' in their name. That will be fixed in the following commit. This closes #669 issue on GitHub.
2022-07-28 14:10:32 +00:00
</para>
</change>
Supporting UNIX sockets in address matching. This closes #645 issue on GitHub. (Also moved a changelog line that was misplaced in a previous commit.)
2022-02-28 11:12:30 +00:00
<change type="feature">
<para>
Reordered changes for 1.28.0 by significance (subjective).
2022-09-13 08:16:55 +00:00
customizable access log format.
Supporting UNIX sockets in address matching. This closes #645 issue on GitHub. (Also moved a changelog line that was misplaced in a previous commit.)
2022-02-28 11:12:30 +00:00
</para>
</change>
Router: forwared header replacement.
2022-06-20 05:22:13 +00:00
<change type="feature">
<para>
Reordered changes for 1.28.0 by significance (subjective).
2022-09-13 08:16:55 +00:00
more HTTP variables support.
Router: forwared header replacement.
2022-06-20 05:22:13 +00:00
</para>
</change>
Var: dynamic variables support. This commit adds the variables $arg_NAME, $header_NAME, and $cookie_NAME.
2022-07-13 20:32:49 +00:00
<change type="feature">
<para>
Reordered changes for 1.28.0 by significance (subjective).
2022-09-13 08:16:55 +00:00
forwarded header to replace client address and protocol.
Var: dynamic variables support. This commit adds the variables $arg_NAME, $header_NAME, and $cookie_NAME.
2022-07-13 20:32:49 +00:00
</para>
</change>
HTTP: added more variables. This commit adds the following variables: $remote_addr, $time_local, $request_line, $status, $body_bytes_sent, $header_referer, $header_user_agent.
2022-07-13 20:34:05 +00:00
<change type="feature">
<para>
Reordered changes for 1.28.0 by significance (subjective).
2022-09-13 08:16:55 +00:00
ability to get dynamic variables.
HTTP: added more variables. This commit adds the following variables: $remote_addr, $time_local, $request_line, $status, $body_bytes_sent, $header_referer, $header_user_agent.
2022-07-13 20:34:05 +00:00
</para>
</change>
Supporting UNIX sockets in address matching. This closes #645 issue on GitHub. (Also moved a changelog line that was misplaced in a previous commit.)
2022-02-28 11:12:30 +00:00
<change type="feature">
<para>
Reordered changes for 1.28.0 by significance (subjective).
2022-09-13 08:16:55 +00:00
support for abstract Unix sockets.
Supporting UNIX sockets in address matching. This closes #645 issue on GitHub. (Also moved a changelog line that was misplaced in a previous commit.)
2022-02-28 11:12:30 +00:00
</para>
</change>
Log: customizable access log format.
2022-07-28 03:05:04 +00:00
<change type="feature">
<para>
Reordered changes for 1.28.0 by significance (subjective).
2022-09-13 08:16:55 +00:00
support for Unix sockets in address matching.
Log: customizable access log format.
2022-07-28 03:05:04 +00:00
</para>
</change>
Implemented basic statistics API.
2022-08-29 06:27:09 +00:00
<change type="feature">
<para>
Reordered changes for 1.28.0 by significance (subjective).
2022-09-13 08:16:55 +00:00
the $dollar variable translates to a literal "$" during variable substitution.
Implemented basic statistics API.
2022-08-29 06:27:09 +00:00
</para>
</change>
Static: Fixed finding the file extension. The code for finding the extension made a few assumptions that are no longer true. It didn't account for pathnames that didn't contain '/', including the empty string, or the NULL string. That code was used with "share", which always had a '/', but now it's also used with "index", which should not have a '/' in it. This fix works by limiting the search to the beginning of the string, so that if no '/' is found in it, it doesn't continue searching before the beginning of the string. This also happens to work for NULL. It is technically Undefined Behavior, as we rely on `NULL + 0 == NULL` and `NULL - NULL == 0`. But that is the only sane behavior for an implementation, and all existing POSIX implementations will Just Work for this code. Relying on this UB is useful, because we don't need to add an explicit check for NULL, and therefore we have faster code. Although the current code can't have a NULL, I expect that when we add support for variables in the index, it will be NULL in some cases. Link: <https://stackoverflow.com/q/67291052/6872717> The same code seems to be defined behavior in C++, which normally will share implementation in the compiler for these cases, and therefore it is really unlikely to be in trouble. Link: <https://stackoverflow.com/q/59409034/6872717>
2022-06-06 12:18:01 +00:00
<change type="bugfix">
<para>
Fixed minor issues in "changes.xml".
2022-09-05 22:55:15 +00:00
router process could crash if index file didn't contain an extension.
Static: Fixed finding the file extension. The code for finding the extension made a few assumptions that are no longer true. It didn't account for pathnames that didn't contain '/', including the empty string, or the NULL string. That code was used with "share", which always had a '/', but now it's also used with "index", which should not have a '/' in it. This fix works by limiting the search to the beginning of the string, so that if no '/' is found in it, it doesn't continue searching before the beginning of the string. This also happens to work for NULL. It is technically Undefined Behavior, as we rely on `NULL + 0 == NULL` and `NULL - NULL == 0`. But that is the only sane behavior for an implementation, and all existing POSIX implementations will Just Work for this code. Relying on this UB is useful, because we don't need to add an explicit check for NULL, and therefore we have faster code. Although the current code can't have a NULL, I expect that when we add support for variables in the index, it will be NULL in some cases. Link: <https://stackoverflow.com/q/67291052/6872717> The same code seems to be defined behavior in C++, which normally will share implementation in the compiler for these cases, and therefore it is really unlikely to be in trouble. Link: <https://stackoverflow.com/q/59409034/6872717>
2022-06-06 12:18:01 +00:00
</para>
</change>
Ruby: fixed contents of SCRIPT_NAME. Having the basename of the script pathname was incorrect. While we don't have something more accurate, the best thing to do is to have it empty (which should be the right thing most of the time). This closes #715 issue on GitHub. The bug was introduced in git commit 0032543fa65f454c471c968998190b027c1ff270 'Ruby: added the Rack environment parameter "SCRIPT_NAME".'.
2022-06-09 12:39:59 +00:00
<change type="bugfix">
<para>
force SCRIPT_NAME in Ruby to always be an empty string.
</para>
</change>
Ruby: fixed segfault on SIGTERM signal. This closes #562 issue on GitHub.
2022-07-28 03:00:15 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.28.0 by significance (subjective).
2022-09-13 08:16:55 +00:00
when isolated PID numbers reach the prototype process host PID,
the prototype crashed.
Ruby: fixed segfault on SIGTERM signal. This closes #562 issue on GitHub.
2022-07-28 03:00:15 +00:00
</para>
</change>
Ruby: prevented a segfault on receiving SIGINT (^C). As was reported[0] by @travisbell on GitHub, if running unit from the terminal in the foreground when hitting ^C to exit it, the ruby application processes would segfault if they were using threads. It's not 100% clear where the actual problem lies, but it _looks_ like it may be in ruby. The simplest way to deal with this for now is to just ignore SIGINT in the ruby application processes. Unit will still receive and handle it, cleanly shutting everything down. For people who want to handle SIGINT in their ruby application running under unit they can still trap SIGINT and it will override the ignore. [0]: https://github.com/nginx/unit/issues/562#issuecomment-1223229585 Closes: https://github.com/nginx/unit/issues/562
2022-08-31 11:49:15 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.28.0 by significance (subjective).
2022-09-13 08:16:55 +00:00
the Ruby application process could crash on SIGTERM.
Ruby: prevented a segfault on receiving SIGINT (^C). As was reported[0] by @travisbell on GitHub, if running unit from the terminal in the foreground when hitting ^C to exit it, the ruby application processes would segfault if they were using threads. It's not 100% clear where the actual problem lies, but it _looks_ like it may be in ruby. The simplest way to deal with this for now is to just ignore SIGINT in the ruby application processes. Unit will still receive and handle it, cleanly shutting everything down. For people who want to handle SIGINT in their ruby application running under unit they can still trap SIGINT and it will override the ignore. [0]: https://github.com/nginx/unit/issues/562#issuecomment-1223229585 Closes: https://github.com/nginx/unit/issues/562
2022-08-31 11:49:15 +00:00
</para>
</change>
Fixing isolated process PID manipulation. Registering an isolated PID in the global PID hash is wrong because it can be duplicated. Isolated processes are stored only in the children list until the response for the WHOAMI message is processed and the global PID is discovered. To remove isolated siblings, a pointer to the children list is introduced in the nxt_process_init_t struct. This closes #633 issue on GitHub.
2022-02-17 12:33:46 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.28.0 by significance (subjective).
2022-09-13 08:16:55 +00:00
the Ruby application process could crash on SIGINT.
Fixing isolated process PID manipulation. Registering an isolated PID in the global PID hash is wrong because it can be duplicated. Isolated processes are stored only in the children list until the response for the WHOAMI message is processed and the global PID is discovered. To remove isolated siblings, a pointer to the children list is introduced in the nxt_process_init_t struct. This closes #633 issue on GitHub.
2022-02-17 12:33:46 +00:00
</para>
</change>
Fixed a mutex leak in the C API. In nxt_unit_create() we could leak a mutex created in nxt_unit_ctx_init(). This could happen if nxt_unit_ctx_init() succeeded but later on we bailed out of nxt_unit_create(), we would destroy the mutex created in nxt_unit_create() but not the one created in nxt_unit_ctx_init(). Reorder things so that we do the call to nxt_unit_create() after all the other checks so if it fails we don't leak the mutex it created. Co-developed-by: Andrew Clayton <a.clayton@f5.com> Signed-off-by: Andrew Clayton <a.clayton@f5.com> Signed-off-by: Alex Colomar <a.colomar@f5.com>
2022-09-09 12:40:17 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.29.0 by significance (subjective).
2022-12-15 12:30:38 +00:00
mutex leak in the C API.
Fixed a mutex leak in the C API. In nxt_unit_create() we could leak a mutex created in nxt_unit_ctx_init(). This could happen if nxt_unit_ctx_init() succeeded but later on we bailed out of nxt_unit_create(), we would destroy the mutex created in nxt_unit_create() but not the one created in nxt_unit_ctx_init(). Reorder things so that we do the call to nxt_unit_create() after all the other checks so if it fails we don't leak the mutex it created. Co-developed-by: Andrew Clayton <a.clayton@f5.com> Signed-off-by: Andrew Clayton <a.clayton@f5.com> Signed-off-by: Alex Colomar <a.colomar@f5.com>
2022-09-09 12:40:17 +00:00
</para>
</change>
Version bump.
2022-06-17 08:46:30 +00:00
</changes>
Version bump.
2021-11-22 04:23:07 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8 unit-python3.9 unit-python3.10
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11 unit-jsc13
unit-jsc14 unit-jsc15 unit-jsc16 unit-jsc17 unit-jsc18"
ver="1.27.0" rev="1"
Specified date of 1.27.0 release in changes.xml.
2022-06-08 12:12:51 +00:00
date="2022-06-02" time="18:00:00 +0300"
Version bump.
2021-11-22 04:23:07 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.27.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.27.0" rev="1"
Specified date of 1.27.0 release in changes.xml.
2022-06-08 12:12:51 +00:00
date="2022-06-02" time="18:00:00 +0300"
Version bump.
2021-11-22 04:23:07 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
Fixed minor issues in "changes.xml".
2022-06-01 13:54:13 +00:00
<change type="feature">
Ruby: added the Rack environment parameter "SCRIPT_NAME".
2022-03-09 05:29:43 +00:00
<para>
Fixed minor issues in "changes.xml".
2022-06-01 13:54:13 +00:00
ability to specify a custom index file name when serving static files.
Ruby: added the Rack environment parameter "SCRIPT_NAME".
2022-03-09 05:29:43 +00:00
</para>
</change>
Fixed minor issues in "changes.xml".
2022-06-01 13:54:13 +00:00
<change type="feature">
Supporting empty Location URIs. An empty string in Location was being handled specially by not sending a Location header. This may occur after variable resolution, so we need to consider this scenario. The obsolete RFC 2616 defined the Location header as consisting of an absolute URI <https://www.rfc-editor.org/rfc/rfc2616#section-14.30>, which cannot be an empty string. However, the current RFC 7231 allows the Location to be a relative URI <https://www.rfc-editor.org/rfc/rfc7231#section-7.1.2>, and a relative URI may be an empty string <https://stackoverflow.com/a/43338457>. Due to these considerations, this patch allows sending an empty Location header without handling this case specially. This behavior will probably be more straightforward to users, too. It also simplifies the code, which is now more readable, fast, and conformant to the current RFC. We're skipping an allocation at request time in a common case such as "action": {"return": 404}
2022-04-09 19:27:12 +00:00
<para>
Fixed minor issues in "changes.xml".
2022-06-01 13:54:13 +00:00
variables support in the "location" option of the "return" action.
Supporting empty Location URIs. An empty string in Location was being handled specially by not sending a Location header. This may occur after variable resolution, so we need to consider this scenario. The obsolete RFC 2616 defined the Location header as consisting of an absolute URI <https://www.rfc-editor.org/rfc/rfc2616#section-14.30>, which cannot be an empty string. However, the current RFC 7231 allows the Location to be a relative URI <https://www.rfc-editor.org/rfc/rfc7231#section-7.1.2>, and a relative URI may be an empty string <https://stackoverflow.com/a/43338457>. Due to these considerations, this patch allows sending an empty Location header without handling this case specially. This behavior will probably be more straightforward to users, too. It also simplifies the code, which is now more readable, fast, and conformant to the current RFC. We're skipping an allocation at request time in a common case such as "action": {"return": 404}
2022-04-09 19:27:12 +00:00
</para>
</change>
Static: supporting new "index" option. This supports a new option "index" that configures a custom index file name to be served when a directory is requested. This initial support only allows a single fixed string. An example: { "share": "/www/data/static/$uri", "index": "lookatthis.htm" } When <example.com/foo/bar/> is requested, </www/data/static/foo/bar/lookatthis.html> is served. Default is "index.html". === nxt_conf_validator.c: Accept "index" as a member of "share", and make sure it's a string. === I tried this feature in my own computer, where I tried the following: - Setting "index" to "lookatthis.htm", and check that the correct file is being served (check both a different name and a different extension). - Not setting "index", and check that <index.html> is being served. - Settind "index" to an array of strings, and check that the configuration fails: { "error": "Invalid configuration.", "detail": "The \"index\" value must be a string, but not an array." }
2021-12-09 02:00:23 +00:00
<change type="feature">
<para>
Fixed minor issues in "changes.xml".
2022-06-01 13:54:13 +00:00
support empty strings in the "location" option of the "return" action.
Static: supporting new "index" option. This supports a new option "index" that configures a custom index file name to be served when a directory is requested. This initial support only allows a single fixed string. An example: { "share": "/www/data/static/$uri", "index": "lookatthis.htm" } When <example.com/foo/bar/> is requested, </www/data/static/foo/bar/lookatthis.html> is served. Default is "index.html". === nxt_conf_validator.c: Accept "index" as a member of "share", and make sure it's a string. === I tried this feature in my own computer, where I tried the following: - Setting "index" to "lookatthis.htm", and check that the correct file is being served (check both a different name and a different extension). - Not setting "index", and check that <index.html> is being served. - Settind "index" to an array of strings, and check that the configuration fails: { "error": "Invalid configuration.", "detail": "The \"index\" value must be a string, but not an array." }
2021-12-09 02:00:23 +00:00
</para>
</change>
Supporting variables in "location". ............ Description: ............ Before this commit, the encoded URI could be calculated at configuration time. Now, since variables can only be resolved at request time, we have different situations: - "location" contains no variables: In this case, we still encode the URI in the conf structure, at configuration time, and then we just copy the resulting string to the ctx structure at request time. - "location" contains variables: In this case, we compile the var string at configure time, then when we resolve it at request time, and then we encode the string. In both cases, as was being done before, if the string is empty, either before or after resolving variables, we skip the encoding. ........... Usefulness: ........... An example of why this feature may be useful is redirecting HTTP to HTTPS with something like: "action": { "return": 301, "location": "https://${host}${uri}" } ..... Bugs: ..... This feature conflicts with the relevant RFCs in the following: '$' is used for Unit variables, but '$' is a reserved character in a URI, to be used as a sub-delimiter. However, it's almost never used as that, and in fact, other parts of Unit already conflict with '$' being a reserved character for use as a sub-delimiter, so this is at least consistent in that sense. VBart suggested an easy workaround if we ever need it: adding a variable '$sign' which resolves to a literal '$'. ...... Notes: ...... An empty string is handled as if "location" wasn't specified at all, so no Location header is sent. This is incorrect, and the code is slightly misleading. The Location header consists of a URI-reference[1], which might be a relative one, which itself might consist of an empty string[2]. [1]: <https://www.rfc-editor.org/rfc/rfc7231#section-7.1.2> [2]: <https://stackoverflow.com/a/43338457> Now that we have variables, it's more likely that an empty Location header will be requested, and we should handle it correctly. I think in a future commit we should modify the code to allow differentiating between an unset "location" and an empty one, which should be treated as any other "location" string. ................. Testing (manual): ................. { "listeners": { "*:80": { "pass": "routes/str" }, "*:81": { "pass": "routes/empty" }, "*:82": { "pass": "routes/var" }, "*:83": { "pass": "routes/enc-str" }, "*:84": { "pass": "routes/enc-var" } }, "routes": { "str": [ { "action": { "return": 301, "location": "foo" } } ], "empty": [ { "action": { "return": 301, "location": "" } } ], "var": [ { "action": { "return": 301, "location": "$host" } } ], "enc-str": [ { "action": { "return": 301, "location": "f%23o#o" } } ], "enc-var": [ { "action": { "return": 301, "location": "f%23o${host}#o" } } ] } } $ curl --dump-header - localhost:80 HTTP/1.1 301 Moved Permanently Location: foo Server: Unit/1.27.0 Date: Thu, 07 Apr 2022 23:30:06 GMT Content-Length: 0 $ curl --dump-header - localhost:81 HTTP/1.1 301 Moved Permanently Server: Unit/1.27.0 Date: Thu, 07 Apr 2022 23:30:08 GMT Content-Length: 0 $ curl --dump-header - localhost:82 HTTP/1.1 301 Moved Permanently Location: localhost Server: Unit/1.27.0 Date: Thu, 07 Apr 2022 23:30:15 GMT Content-Length: 0 $ curl --dump-header - -H "Host: bar" localhost:82 HTTP/1.1 301 Moved Permanently Location: bar Server: Unit/1.27.0 Date: Thu, 07 Apr 2022 23:30:23 GMT Content-Length: 0 $ curl --dump-header - -H "Host: " localhost:82 HTTP/1.1 301 Moved Permanently Server: Unit/1.27.0 Date: Thu, 07 Apr 2022 23:30:29 GMT Content-Length: 0 $ curl --dump-header - localhost:83 HTTP/1.1 301 Moved Permanently Location: f%23o#o Server: Unit/1.27.0 Date: Sat, 09 Apr 2022 11:22:23 GMT Content-Length: 0 $ curl --dump-header - -H "Host: " localhost:84 HTTP/1.1 301 Moved Permanently Location: f%23o#o Server: Unit/1.27.0 Date: Sat, 09 Apr 2022 11:22:44 GMT Content-Length: 0 $ curl --dump-header - -H "Host: alx" localhost:84 HTTP/1.1 301 Moved Permanently Location: f%23oalx#o Server: Unit/1.27.0 Date: Sat, 09 Apr 2022 11:22:52 GMT Content-Length: 0 $ curl --dump-header - -H "Host: a#l%23x" localhost:84 HTTP/1.1 301 Moved Permanently Location: f%2523oa#l%2523x%23o Server: Unit/1.27.0 Date: Sat, 09 Apr 2022 11:23:09 GMT Content-Length: 0 $ curl --dump-header - -H "Host: b##ar" localhost:82 HTTP/1.1 301 Moved Permanently Location: b#%23ar Server: Unit/1.27.0 Date: Sat, 09 Apr 2022 11:25:01 GMT Content-Length: 0
2022-04-05 09:47:56 +00:00
<change type="feature">
<para>
Fixed minor issues in "changes.xml".
2022-06-01 13:54:13 +00:00
added a new variable, $request_uri, that includes both the path and the query
parts as per RFC 3986, sections 3-4.
Supporting variables in "location". ............ Description: ............ Before this commit, the encoded URI could be calculated at configuration time. Now, since variables can only be resolved at request time, we have different situations: - "location" contains no variables: In this case, we still encode the URI in the conf structure, at configuration time, and then we just copy the resulting string to the ctx structure at request time. - "location" contains variables: In this case, we compile the var string at configure time, then when we resolve it at request time, and then we encode the string. In both cases, as was being done before, if the string is empty, either before or after resolving variables, we skip the encoding. ........... Usefulness: ........... An example of why this feature may be useful is redirecting HTTP to HTTPS with something like: "action": { "return": 301, "location": "https://${host}${uri}" } ..... Bugs: ..... This feature conflicts with the relevant RFCs in the following: '$' is used for Unit variables, but '$' is a reserved character in a URI, to be used as a sub-delimiter. However, it's almost never used as that, and in fact, other parts of Unit already conflict with '$' being a reserved character for use as a sub-delimiter, so this is at least consistent in that sense. VBart suggested an easy workaround if we ever need it: adding a variable '$sign' which resolves to a literal '$'. ...... Notes: ...... An empty string is handled as if "location" wasn't specified at all, so no Location header is sent. This is incorrect, and the code is slightly misleading. The Location header consists of a URI-reference[1], which might be a relative one, which itself might consist of an empty string[2]. [1]: <https://www.rfc-editor.org/rfc/rfc7231#section-7.1.2> [2]: <https://stackoverflow.com/a/43338457> Now that we have variables, it's more likely that an empty Location header will be requested, and we should handle it correctly. I think in a future commit we should modify the code to allow differentiating between an unset "location" and an empty one, which should be treated as any other "location" string. ................. Testing (manual): ................. { "listeners": { "*:80": { "pass": "routes/str" }, "*:81": { "pass": "routes/empty" }, "*:82": { "pass": "routes/var" }, "*:83": { "pass": "routes/enc-str" }, "*:84": { "pass": "routes/enc-var" } }, "routes": { "str": [ { "action": { "return": 301, "location": "foo" } } ], "empty": [ { "action": { "return": 301, "location": "" } } ], "var": [ { "action": { "return": 301, "location": "$host" } } ], "enc-str": [ { "action": { "return": 301, "location": "f%23o#o" } } ], "enc-var": [ { "action": { "return": 301, "location": "f%23o${host}#o" } } ] } } $ curl --dump-header - localhost:80 HTTP/1.1 301 Moved Permanently Location: foo Server: Unit/1.27.0 Date: Thu, 07 Apr 2022 23:30:06 GMT Content-Length: 0 $ curl --dump-header - localhost:81 HTTP/1.1 301 Moved Permanently Server: Unit/1.27.0 Date: Thu, 07 Apr 2022 23:30:08 GMT Content-Length: 0 $ curl --dump-header - localhost:82 HTTP/1.1 301 Moved Permanently Location: localhost Server: Unit/1.27.0 Date: Thu, 07 Apr 2022 23:30:15 GMT Content-Length: 0 $ curl --dump-header - -H "Host: bar" localhost:82 HTTP/1.1 301 Moved Permanently Location: bar Server: Unit/1.27.0 Date: Thu, 07 Apr 2022 23:30:23 GMT Content-Length: 0 $ curl --dump-header - -H "Host: " localhost:82 HTTP/1.1 301 Moved Permanently Server: Unit/1.27.0 Date: Thu, 07 Apr 2022 23:30:29 GMT Content-Length: 0 $ curl --dump-header - localhost:83 HTTP/1.1 301 Moved Permanently Location: f%23o#o Server: Unit/1.27.0 Date: Sat, 09 Apr 2022 11:22:23 GMT Content-Length: 0 $ curl --dump-header - -H "Host: " localhost:84 HTTP/1.1 301 Moved Permanently Location: f%23o#o Server: Unit/1.27.0 Date: Sat, 09 Apr 2022 11:22:44 GMT Content-Length: 0 $ curl --dump-header - -H "Host: alx" localhost:84 HTTP/1.1 301 Moved Permanently Location: f%23oalx#o Server: Unit/1.27.0 Date: Sat, 09 Apr 2022 11:22:52 GMT Content-Length: 0 $ curl --dump-header - -H "Host: a#l%23x" localhost:84 HTTP/1.1 301 Moved Permanently Location: f%2523oa#l%2523x%23o Server: Unit/1.27.0 Date: Sat, 09 Apr 2022 11:23:09 GMT Content-Length: 0 $ curl --dump-header - -H "Host: b##ar" localhost:82 HTTP/1.1 301 Moved Permanently Location: b#%23ar Server: Unit/1.27.0 Date: Sat, 09 Apr 2022 11:25:01 GMT Content-Length: 0
2022-04-05 09:47:56 +00:00
</para>
</change>
Var: Added $request_uri (as in NGINX). This supports a new variable $request_uri that contains the path and the query (See RFC 3986, section 3). Its contents are percent encoded. This is useful for example to redirect HTTP to HTTPS: { "return": "301", "location": "https://$host$request_uri" } When <http://example.com/foo%23bar?baz> is requested, the server redirects to <https://example.com/foo%23bar?baz>. === Testing: //diff --git a/src/nxt_http_return.c b/src/nxt_http_return.c //index 82c9156..adeb3a1 100644 //--- a/src/nxt_http_return.c //+++ b/src/nxt_http_return.c //@@ -196,6 +196,7 @@ nxt_http_return_send_ready(nxt_task_t *task, void *obj, void *data) // field->value = ctx->encoded.start; // field->value_length = ctx->encoded.length; // } //+ fprintf(stderr, "ALX: target[%1$i]: <%2$.*1$s>\n", (int)r->target.length, r->target.start); // // r->state = &nxt_http_return_send_state; // { "listeners": { "*:81": { "pass": "routes/ru" } }, "routes": { "ru": [{ "action": { "return": 301, "location": "$request_uri" } }] } } $ curl -i http://localhost:81/*foo%2Abar?baz#arg HTTP/1.1 301 Moved Permanently Location: /*foo%2Abar?baz Server: Unit/1.27.0 Date: Mon, 30 May 2022 16:04:30 GMT Content-Length: 0 $ sudo cat /usr/local/unit.log | grep ALX ALX: target[15]: </*foo%2Abar?baz>
2022-05-26 12:38:42 +00:00
<change type="feature">
<para>
Fixed minor issues in "changes.xml".
2022-06-01 13:54:13 +00:00
Ruby Rack environment parameter "SCRIPT_NAME" support.
Var: Added $request_uri (as in NGINX). This supports a new variable $request_uri that contains the path and the query (See RFC 3986, section 3). Its contents are percent encoded. This is useful for example to redirect HTTP to HTTPS: { "return": "301", "location": "https://$host$request_uri" } When <http://example.com/foo%23bar?baz> is requested, the server redirects to <https://example.com/foo%23bar?baz>. === Testing: //diff --git a/src/nxt_http_return.c b/src/nxt_http_return.c //index 82c9156..adeb3a1 100644 //--- a/src/nxt_http_return.c //+++ b/src/nxt_http_return.c //@@ -196,6 +196,7 @@ nxt_http_return_send_ready(nxt_task_t *task, void *obj, void *data) // field->value = ctx->encoded.start; // field->value_length = ctx->encoded.length; // } //+ fprintf(stderr, "ALX: target[%1$i]: <%2$.*1$s>\n", (int)r->target.length, r->target.start); // // r->state = &nxt_http_return_send_state; // { "listeners": { "*:81": { "pass": "routes/ru" } }, "routes": { "ru": [{ "action": { "return": 301, "location": "$request_uri" } }] } } $ curl -i http://localhost:81/*foo%2Abar?baz#arg HTTP/1.1 301 Moved Permanently Location: /*foo%2Abar?baz Server: Unit/1.27.0 Date: Mon, 30 May 2022 16:04:30 GMT Content-Length: 0 $ sudo cat /usr/local/unit.log | grep ALX ALX: target[15]: </*foo%2Abar?baz>
2022-05-26 12:38:42 +00:00
</para>
</change>
Workaround for the warning in nxt_realloc() on GCC 12. This closes #639 issue on Github.
2022-02-22 11:18:18 +00:00
<change type="feature">
<para>
compatibility with GCC 12.
</para>
</change>
Ruby: added stream IO "close" required by Rack specification. This closes #654 issue on Github.
2022-05-13 11:33:40 +00:00
<change type="bugfix">
<para>
Ruby Sinatra applications don't work without custom logging.
</para>
</change>
Certificates: fixed crash when reallocating chain.
2022-02-14 12:14:03 +00:00
<change type="bugfix">
<para>
Fixed minor issues in "changes.xml".
2022-06-01 13:54:13 +00:00
the controller process could crash when a chain of more than four
Certificates: fixed crash when reallocating chain.
2022-02-14 12:14:03 +00:00
certificates was uploaded.
</para>
</change>
Perl: creating input and error streams if closed. Application handler can do anything with a stream object (including close it). Once the stream is closed, Unit creates a new stream. This closes #616 issue on GitHub.
2021-12-27 13:37:35 +00:00
<change type="bugfix">
<para>
some Perl applications failed to process the request body, notably with Plack.
</para>
</change>
Java: fixing multiple SCI initializations. - Ignoring Tomcat WebSocket container initialization. - Renaming application class loader to UnitClassLoader to avoid development environment enablement in Spring Boot. This closes #609 issue on GitHub.
2021-12-27 13:37:36 +00:00
<change type="bugfix">
<para>
some Spring Boot applications failed to start, notably with Grails.
</para>
</change>
Python: fixing incorrect function object dereference. The __call__ method can be native and not be a PyFunction type. A type check is thus required before accessing op_code and other fields. Reproduced on Ubuntu 21.04, Python 3.9.4 and Falcon framework: here, the App.__call__ method is compiled with Cython, so accessing op_code->co_flags is invalid; accidentally, the COROUTINE bit is set which forces the Python module into the ASGI mode. The workaround is explicit protocol specification. Note: it is impossible to specify the legacy mode for ASGI.
2022-02-08 09:04:41 +00:00
<change type="bugfix">
<para>
incorrect Python protocol auto detection (ASGI or WSGI) for native callable
object, notably with Falcon.
</para>
</change>
Node.js: fixed ES modules format in loader.mjs. Before Node.js v16.14.0 the "format" value in defaultResolve was ignored so error was hidden. For more information see: https://github.com/nodejs/node/pull/40980
2022-06-02 10:48:27 +00:00
<change type="bugfix">
<para>
ECMAScript modules did not work with the recent Node.js versions.
</para>
</change>
Merged with the 1.26 branch.
2021-12-03 00:10:15 +00:00
</changes>
Version bump.
2021-12-02 14:16:05 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8 unit-python3.9 unit-python3.10
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11 unit-jsc13
unit-jsc14 unit-jsc15 unit-jsc16 unit-jsc17 unit-jsc18"
ver="1.26.1" rev="1"
Added version 1.26.1 CHANGES.
2021-12-02 15:22:57 +00:00
date="2021-12-02" time="18:00:00 +0300"
Version bump.
2021-12-02 14:16:05 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
Fixing access_log structure reference counting. The reference to the access_log structure is stored in the current nxt_router_conf_t and the global nxt_router_t. When the reference is copied, the reference counter should be adjusted accordingly. This closes #593 issue on GitHub.
2021-11-25 13:58:43 +00:00
<para>
Version bump.
2021-12-02 14:16:05 +00:00
NGINX Unit updated to 1.26.1.
Fixing access_log structure reference counting. The reference to the access_log structure is stored in the current nxt_router_conf_t and the global nxt_router_t. When the reference is copied, the reference counter should be adjusted accordingly. This closes #593 issue on GitHub.
2021-11-25 13:58:43 +00:00
</para>
</change>
Version bump.
2021-12-02 14:16:05 +00:00
</changes>
<changes apply="unit" ver="1.26.1" rev="1"
Added version 1.26.1 CHANGES.
2021-12-02 15:22:57 +00:00
date="2021-12-02" time="18:00:00 +0300"
Version bump.
2021-12-02 14:16:05 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
Added a changelog for 730e903f4534.
2021-11-25 13:58:45 +00:00
<change type="bugfix">
<para>
occasionally, the Unit daemon was unable to fully terminate; the bug had
appeared in 1.26.0.
</para>
</change>
PHP: fixed crash when calling module functions in OPcache preload. In PHP, custom fastcgi_finish_request() and overloaded chdir() functions can be invoked by an OPcache preloading script (it runs when php_module_startup() is called in the app process setup handler). In this case, there was no runtime context set so trying to access it caused a segmentation fault. This closes #602 issue on GitHub.
2021-11-25 16:58:54 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.26.1 by significance (subjective).
2021-12-02 15:22:48 +00:00
a prototype process could crash on an application process exit; the bug had
Added a changelog for 730e903f4534.
2021-11-25 13:58:45 +00:00
appeared in 1.26.0.
PHP: fixed crash when calling module functions in OPcache preload. In PHP, custom fastcgi_finish_request() and overloaded chdir() functions can be invoked by an OPcache preloading script (it runs when php_module_startup() is called in the app process setup handler). In this case, there was no runtime context set so trying to access it caused a segmentation fault. This closes #602 issue on GitHub.
2021-11-25 16:58:54 +00:00
</para>
</change>
Fixing prototype process crash. A prototype stores linked application processes structures. When an application process terminates, it's removed from the list. To avoid double removal, the pointer to the next element should be set to NULL. The issue was introduced in c8790d2a89bb.
2021-12-01 15:05:50 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.26.1 by significance (subjective).
2021-12-02 15:22:48 +00:00
the router process crashed on reconfiguration if "access_log" was configured
without listeners.
PHP: fixed crash when calling module functions in OPcache preload. In PHP, custom fastcgi_finish_request() and overloaded chdir() functions can be invoked by an OPcache preloading script (it runs when php_module_startup() is called in the app process setup handler). In this case, there was no runtime context set so trying to access it caused a segmentation fault. This closes #602 issue on GitHub.
2021-11-25 16:58:54 +00:00
</para>
</change>
Fixing prototype process crash. A prototype stores linked application processes structures. When an application process terminates, it's removed from the list. To avoid double removal, the pointer to the next element should be set to NULL. The issue was introduced in c8790d2a89bb.
2021-12-01 15:05:50 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.26.1 by significance (subjective).
2021-12-02 15:22:48 +00:00
a segmentation fault occurred in the PHP module if chdir() or
fastcgi_finish_request() was called in the OPcache preloading script.
Fixing prototype process crash. A prototype stores linked application processes structures. When an application process terminates, it's removed from the list. To avoid double removal, the pointer to the next element should be set to NULL. The issue was introduced in c8790d2a89bb.
2021-12-01 15:05:50 +00:00
</para>
</change>
Disabling SCM_CREDS usage on DragonFly BSD. DragonFly BSD supports SCM_CREDS and SCM_RIGHTS, but only the first control message is passed correctly while the second one isn't processed by the kernel. This closes #599 issue on GitHub.
2021-12-01 15:06:38 +00:00
<change type="bugfix">
<para>
fatal errors on DragonFly BSD; the bug had appeared in 1.26.0.
</para>
</change>
Version bump.
2021-11-22 04:23:07 +00:00
</changes>
Packages: added Ubuntu 21.10 "impish" support.
2021-10-21 10:23:25 +00:00
<changes apply="unit-jsc18" ver="1.26.0" rev="1"
Added version 1.26.0 CHANGES.
2021-11-18 12:48:02 +00:00
date="2021-11-18" time="18:00:00 +0300"
Packages: added Ubuntu 21.10 "impish" support.
2021-10-21 10:23:25 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Java 18 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-python3.10" ver="1.26.0" rev="1"
Added version 1.26.0 CHANGES.
2021-11-18 12:48:02 +00:00
date="2021-11-18" time="18:00:00 +0300"
Packages: added Ubuntu 21.10 "impish" support.
2021-10-21 10:23:25 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Python 3.10 module for NGINX Unit.
</para>
</change>
</changes>
Version bump.
2021-08-24 11:38:24 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8 unit-python3.9
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11 unit-jsc13
unit-jsc14 unit-jsc15 unit-jsc16 unit-jsc17"
ver="1.26.0" rev="1"
Added version 1.26.0 CHANGES.
2021-11-18 12:48:02 +00:00
date="2021-11-18" time="18:00:00 +0300"
Version bump.
2021-08-24 11:38:24 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.26.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.26.0" rev="1"
Added version 1.26.0 CHANGES.
2021-11-18 12:48:02 +00:00
date="2021-11-18" time="18:00:00 +0300"
Version bump.
2021-08-24 11:38:24 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
Static: variables in the "share" option. This commit supports variable in the "share" option, the finding path to file serve is the value from "share". An example: { "share": "/www/data/static$uri" }
2021-09-30 14:17:28 +00:00
<change type="change">
<para>
the "share" option now specifies the entire path to the files it serves,
rather than a document root directory to be prepended to the request URI.
</para>
</change>
<change type="feature">
<para>
Reordered changes for 1.26.0 by significance (subjective).
2021-11-18 12:48:02 +00:00
automatic adjustment of existing configurations to the new "share" behavior
when updating from previous versions.
Static: variables in the "share" option. This commit supports variable in the "share" option, the finding path to file serve is the value from "share". An example: { "share": "/www/data/static$uri" }
2021-09-30 14:17:28 +00:00
</para>
</change>
Static: multiple paths in the "share" option.
2021-10-01 02:03:55 +00:00
<change type="feature">
<para>
Reordered changes for 1.26.0 by significance (subjective).
2021-11-18 12:48:02 +00:00
variables support in the "share" option.
Static: multiple paths in the "share" option.
2021-10-01 02:03:55 +00:00
</para>
</change>
Static: variables in the "chroot" option.
2021-09-28 15:08:26 +00:00
<change type="feature">
<para>
Reordered changes for 1.26.0 by significance (subjective).
2021-11-18 12:48:02 +00:00
multiple paths in the "share" option.
Static: variables in the "chroot" option.
2021-09-28 15:08:26 +00:00
</para>
</change>
Configuration: automatic migration to the new "share" behavior.
2021-10-09 02:44:31 +00:00
<change type="feature">
<para>
Reordered changes for 1.26.0 by significance (subjective).
2021-11-18 12:48:02 +00:00
variables support in the "chroot" option.
Configuration: automatic migration to the new "share" behavior.
2021-10-09 02:44:31 +00:00
</para>
</change>
Router: matching query string support. The "query" option matches decoded arguments, including plus ('+') to space (' '). Like "uri", it can be a string or an array of strings.
2021-11-05 14:56:34 +00:00
<change type="feature">
<para>
Reordered changes for 1.26.0 by significance (subjective).
2021-11-18 12:48:02 +00:00
PHP opcache is shared between application processes.
Router: matching query string support. The "query" option matches decoded arguments, including plus ('+') to space (' '). Like "uri", it can be a string or an array of strings.
2021-11-05 14:56:34 +00:00
</para>
</change>
Introducing application prototype processes.
2021-11-09 12:48:44 +00:00
<change type="feature">
<para>
Reordered changes for 1.26.0 by significance (subjective).
2021-11-18 12:48:02 +00:00
request routing by the query string.
Introducing application prototype processes.
2021-11-09 12:48:44 +00:00
</para>
</change>
Fixing build with glibc 2.34. Explicitly using the sysconf() call to obtain the minimum thread stack size instead of the PTHREAD_STACK_MIN macro. This closes #576 PR on GitHub.
2021-09-14 16:35:49 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.26.0 by significance (subjective).
2021-11-18 12:48:02 +00:00
the router and app processes could crash when the requests limit was reached
by asynchronous or multithreaded apps.
Fixing build with glibc 2.34. Explicitly using the sysconf() call to obtain the minimum thread stack size instead of the PTHREAD_STACK_MIN macro. This closes #576 PR on GitHub.
2021-09-14 16:35:49 +00:00
</para>
</change>
Fixed WebSocket connection hang issue after listener reconfigure. Because the configuration values were read from the listener's configuration, an established WebSocket connection was unable to work properly (i. e. stuck) if the listener was removed. The correct source of configuration values is the request config joint. This is related to issue #581 on GitHub.
2021-09-20 06:01:08 +00:00
<change type="bugfix">
<para>
established WebSocket connections could stop reading frames from the client
after the corresponding listener had been reconfigured.
</para>
</change>
Moving change record to the right place. The change record was incorectly merged in 43553aa72111.
2021-11-08 20:04:36 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.26.0 by significance (subjective).
2021-11-18 12:48:02 +00:00
fixed building with glibc 2.34, notably Fedora 35.
Moving change record to the right place. The change record was incorectly merged in 43553aa72111.
2021-11-08 20:04:36 +00:00
</para>
</change>
Version bump.
2021-08-24 11:38:24 +00:00
</changes>
Version bump.
2021-05-28 15:16:23 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8 unit-python3.9
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11 unit-jsc13
unit-jsc14 unit-jsc15 unit-jsc16 unit-jsc17"
ver="1.25.0" rev="1"
Added version 1.25.0 CHANGES.
2021-08-19 14:48:21 +00:00
date="2021-08-19" time="18:00:00 +0300"
Version bump.
2021-05-28 15:16:23 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.25.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.25.0" rev="1"
Added version 1.25.0 CHANGES.
2021-08-19 14:48:21 +00:00
date="2021-08-19" time="18:00:00 +0300"
Version bump.
2021-05-28 15:16:23 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
Added TLS session tickets support.
2021-08-17 23:52:32 +00:00
<change type="feature">
<para>
Reordered changes for 1.25.0 by significance (subjective).
2021-08-19 14:43:04 +00:00
client IP address replacement from a specified HTTP header field.
Added TLS session tickets support.
2021-08-17 23:52:32 +00:00
</para>
</change>
Enabling configure TLS sessions. To support TLS sessions, Unit uses the OpenSSL built-in session cache; the cache_size option defines the number sessions to store. To disable the feather, the option must be zero.
2021-07-21 22:22:52 +00:00
<change type="feature">
<para>
TLS sessions cache.
</para>
</change>
Ruby: process and thread lifecycle hooks. This feature allows one to specify blocks of code that are called when certain lifecycle events occur. A user configures a "hooks" property on the app configuration that points to a script. This script will be evaluated on boot and should contain blocks of code that will be called on specific events. An example of configuration: { "type": "ruby", "processes": 2, "threads": 2, "user": "vagrant", "group": "vagrant", "script": "config.ru", "hooks": "hooks.rb", "working_directory": "/home/vagrant/unit/rbhooks", "environment": { "GEM_HOME": "/home/vagrant/.ruby" } } An example of a valid "hooks.rb" file follows: File.write("./hooks.#{Process.pid}", "hooks evaluated") on_worker_boot do File.write("./worker_boot.#{Process.pid}", "worker booted") end on_thread_boot do File.write("./thread_boot.#{Process.pid}.#{Thread.current.object_id}", "thread booted") end on_thread_shutdown do File.write("./thread_shutdown.#{Process.pid}.#{Thread.current.object_id}", "thread shutdown") end on_worker_shutdown do File.write("./worker_shutdown.#{Process.pid}", "worker shutdown") end This closes issue #535 on GitHub.
2021-07-02 12:57:55 +00:00
<change type="feature">
<para>
Reordered changes for 1.25.0 by significance (subjective).
2021-08-19 14:43:04 +00:00
TLS session tickets.
Ruby: process and thread lifecycle hooks. This feature allows one to specify blocks of code that are called when certain lifecycle events occur. A user configures a "hooks" property on the app configuration that points to a script. This script will be evaluated on boot and should contain blocks of code that will be called on specific events. An example of configuration: { "type": "ruby", "processes": 2, "threads": 2, "user": "vagrant", "group": "vagrant", "script": "config.ru", "hooks": "hooks.rb", "working_directory": "/home/vagrant/unit/rbhooks", "environment": { "GEM_HOME": "/home/vagrant/.ruby" } } An example of a valid "hooks.rb" file follows: File.write("./hooks.#{Process.pid}", "hooks evaluated") on_worker_boot do File.write("./worker_boot.#{Process.pid}", "worker booted") end on_thread_boot do File.write("./thread_boot.#{Process.pid}.#{Thread.current.object_id}", "thread booted") end on_thread_shutdown do File.write("./thread_shutdown.#{Process.pid}.#{Thread.current.object_id}", "thread shutdown") end on_worker_shutdown do File.write("./worker_shutdown.#{Process.pid}", "worker shutdown") end This closes issue #535 on GitHub.
2021-07-02 12:57:55 +00:00
</para>
</change>
Application restart introduced. When processing a restart request, the router sends a QUIT message to all existing processes of the application. Then, a new shared application port is created to ensure that new requests won't be handled by the old processes of the application.
2021-07-29 16:50:39 +00:00
<change type="feature">
<para>
application restart control.
</para>
</change>
Router: client IP address replacement. This commit introduces the replacement of the client address based on the value of a specified HTTP header. This is intended for use when Unit is placed behind a reverse proxy like nginx or a CDN. You must specify the source addresses of the trusted proxies. This can be accomplished with any valid IP pattern supported by Unit's match block: ["10.0.0.1", "10.4.0.0/16", "!192.168.1.1"] The feature is configured per listener. The client address replacement functionality only operates when there is a source IP match and the specified header is present. Typically this would be an 'X-Forwarded-For' header. { "listeners": { "127.0.0.1:8080": { "client_ip": { "header": "X-Forwarded-For", "source": [ "10.0.0.0/8" ] }, "pass": "applications/my_app" }, } } If a request occurs and Unit receives a header like below: "X-Forwarded-For: 84.123.23.23" By default, Unit trusts the last rightmost IP in the header, so REMOTE_ADDR will be set to 84.123.23.23 if the connection originated from 10.0.0.0/8. If Unit runs behind consecutive reverse proxies and receives a header similar to the following: "X-Forwarded-For: 84.123.23.23, 10.0.0.254" You will need to enable "recursive" checking, which walks the header from last address to first and chooses the first non-trusted address it finds. { "listeners": { "127.0.0.1:8080": { "client_ip": { "header": "X-Forwarded-For", "source": [ "10.0.0.0/8" ] "recursive": true, }, "pass": "applications/my_app" }, } } If a connection from 10.0.0.0/8 occurs, the chain is walked. Here, 10.0.0.254 is also a trusted address so the client address will be replaced with 84.123.23.23. If all IP addresses in the header are trusted, the client address is set to the first address in the header: If 10.0.0.0/8 is trusted and "X-Forwarded-For: 10.0.0.3, 10.0.0.2, 10.0.0.1", the client address will be replaced with 10.0.0.3.
2021-08-12 08:23:16 +00:00
<change type="feature">
<para>
Reordered changes for 1.25.0 by significance (subjective).
2021-08-19 14:43:04 +00:00
process and thread lifecycle hooks in Ruby.
Router: client IP address replacement. This commit introduces the replacement of the client address based on the value of a specified HTTP header. This is intended for use when Unit is placed behind a reverse proxy like nginx or a CDN. You must specify the source addresses of the trusted proxies. This can be accomplished with any valid IP pattern supported by Unit's match block: ["10.0.0.1", "10.4.0.0/16", "!192.168.1.1"] The feature is configured per listener. The client address replacement functionality only operates when there is a source IP match and the specified header is present. Typically this would be an 'X-Forwarded-For' header. { "listeners": { "127.0.0.1:8080": { "client_ip": { "header": "X-Forwarded-For", "source": [ "10.0.0.0/8" ] }, "pass": "applications/my_app" }, } } If a request occurs and Unit receives a header like below: "X-Forwarded-For: 84.123.23.23" By default, Unit trusts the last rightmost IP in the header, so REMOTE_ADDR will be set to 84.123.23.23 if the connection originated from 10.0.0.0/8. If Unit runs behind consecutive reverse proxies and receives a header similar to the following: "X-Forwarded-For: 84.123.23.23, 10.0.0.254" You will need to enable "recursive" checking, which walks the header from last address to first and chooses the first non-trusted address it finds. { "listeners": { "127.0.0.1:8080": { "client_ip": { "header": "X-Forwarded-For", "source": [ "10.0.0.0/8" ] "recursive": true, }, "pass": "applications/my_app" }, } } If a connection from 10.0.0.0/8 occurs, the chain is walked. Here, 10.0.0.254 is also a trusted address so the client address will be replaced with 84.123.23.23. If all IP addresses in the header are trusted, the client address is set to the first address in the header: If 10.0.0.0/8 is trusted and "X-Forwarded-For: 10.0.0.3, 10.0.0.2, 10.0.0.1", the client address will be replaced with 10.0.0.3.
2021-08-12 08:23:16 +00:00
</para>
</change>
Changing SNI callback return code if a client sends no SNI. When a client sends no SNI is a common situation. But currently the server processes it as an error and returns SSL_TLSEXT_ERR_ALERT_FATAL causing termination of a current TLS session. The problem occurs if configuration has more than one certificate bundle in a listener. This fix changes the return code to SSL_TLSEXT_ERR_OK and the log level of a message.
2021-07-22 18:23:48 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.25.0 by significance (subjective).
2021-08-19 14:43:04 +00:00
the router process could crash on TLS connection open when multiple listeners
with TLS certificates were configured; the bug had appeared in 1.23.0.
Changing SNI callback return code if a client sends no SNI. When a client sends no SNI is a common situation. But currently the server processes it as an error and returns SSL_TLSEXT_ERR_ALERT_FATAL causing termination of a current TLS session. The problem occurs if configuration has more than one certificate bundle in a listener. This fix changes the return code to SSL_TLSEXT_ERR_OK and the log level of a message.
2021-07-22 18:23:48 +00:00
</para>
</change>
Fixing memory and descriptor leakage in case of port send failure. In rare cases, when the destination process had finished running but no notification of this was received yet, send could fail with an error, and the send message structure with file descriptors could leak. The leakage was periodically reproduced by respawn tests on FreeBSD 12.
2021-07-01 13:23:51 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.25.0 by significance (subjective).
2021-08-19 14:43:04 +00:00
TLS connections were rejected for configurations with multiple certificate
bundles in a listener if the client did not use SNI.
Fixing memory and descriptor leakage in case of port send failure. In rare cases, when the destination process had finished running but no notification of this was received yet, send could fail with an error, and the send message structure with file descriptors could leak. The leakage was periodically reproduced by respawn tests on FreeBSD 12.
2021-07-01 13:23:51 +00:00
</para>
</change>
Router: fixing assertion on app thread port handle. A new application thread port message can be processed in the router after the application is removed from the router. Assertion for this case is replaced by a condition to store the new thread port until receiving the stop notification from the application process.
2021-07-19 13:23:13 +00:00
<change type="bugfix">
<para>
Fixed a typo in changes.xml.
2021-08-20 03:56:53 +00:00
the router process could crash with frequent multithreaded application
Router: fixing assertion on app thread port handle. A new application thread port message can be processed in the router after the application is removed from the router. Assertion for this case is replaced by a condition to store the new thread port until receiving the stop notification from the application process.
2021-07-19 13:23:13 +00:00
reconfiguration.
</para>
</change>
Fixing memory and descriptor leakage in case of port send failure. In rare cases, when the destination process had finished running but no notification of this was received yet, send could fail with an error, and the send message structure with file descriptors could leak. The leakage was periodically reproduced by respawn tests on FreeBSD 12.
2021-07-01 13:23:51 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.25.0 by significance (subjective).
2021-08-19 14:43:04 +00:00
compatibility issues with some Python ASGI apps, notably based on the Starlette
framework.
Fixing memory and descriptor leakage in case of port send failure. In rare cases, when the destination process had finished running but no notification of this was received yet, send could fail with an error, and the send message structure with file descriptors could leak. The leakage was periodically reproduced by respawn tests on FreeBSD 12.
2021-07-01 13:23:51 +00:00
</para>
</change>
Fixing crash during IPv6 text address generation. When the textual representation of an IPv6 nxt_sockaddr_t was being generated, a crash would occur if the address had a full IPv6 form: f607:7403:1e4b:6c66:33b2:843f:2517:da27 This was caused by a variable that tracks the location of a collapsed group ("::") that was not set to a sane default. When the address was generated, a group would be inserted when it was not necessary, thus causing an overflow. This closes #481 issue on GitHub.
2021-07-02 10:55:13 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.25.0 by significance (subjective).
2021-08-19 14:43:04 +00:00
a descriptor and memory leak occurred in the router process when an app process
stopped or crashed.
Fixing crash during IPv6 text address generation. When the textual representation of an IPv6 nxt_sockaddr_t was being generated, a crash would occur if the address had a full IPv6 form: f607:7403:1e4b:6c66:33b2:843f:2517:da27 This was caused by a variable that tracks the location of a collapsed group ("::") that was not set to a sane default. When the address was generated, a group would be inserted when it was not necessary, thus causing an overflow. This closes #481 issue on GitHub.
2021-07-02 10:55:13 +00:00
</para>
</change>
Python: fixing ASGI receive() issues. The receive() call never blocks for a GET request and always returns the same empty body message. The Starlette framework creates a separate task when receive() is called in a loop until an 'http.disconnect' message is received. The 'http.disconnect' message was previously issued after the response header had been sent. However, the correct behavior is to respond with 'http.disconnect' after sending the response is complete. This closes #564 issue on GitHub.
2021-07-20 07:37:50 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.25.0 by significance (subjective).
2021-08-19 14:43:04 +00:00
the controller or router process could crash if the configuration contained
a full-form IPv6 in a listener address.
Python: fixing ASGI receive() issues. The receive() call never blocks for a GET request and always returns the same empty body message. The Starlette framework creates a separate task when receive() is called in a loop until an 'http.disconnect' message is received. The 'http.disconnect' message was previously issued after the response header had been sent. However, the correct behavior is to respond with 'http.disconnect' after sending the response is complete. This closes #564 issue on GitHub.
2021-07-20 07:37:50 +00:00
</para>
</change>
Added a changelog for ae4f067a9ea4.
2021-08-04 10:09:50 +00:00
<change type="bugfix">
<para>
the router process crashed when a request was passed to an empty "routes"
or "upstreams" using a variable "pass" option.
</para>
</change>
Router: fixed crash when matching an empty address pattern array. A crash would occur when the router tried to match an against an empty address pattern array. The following configuration was used to reproduce the issue: { "listeners": { "127.0.0.1:8082": { "pass": "routes" } }, "routes": [ { "match": { "source": [] }, "action": { "return": 200 } } ] }
2021-08-05 16:00:01 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.25.0 by significance (subjective).
2021-08-19 14:43:04 +00:00
the router process crashed while matching a request to an empty array of source
or destination address patterns.
Router: fixed crash when matching an empty address pattern array. A crash would occur when the router tried to match an against an empty address pattern array. The following configuration was used to reproduce the issue: { "listeners": { "127.0.0.1:8082": { "pass": "routes" } }, "routes": [ { "match": { "source": [] }, "action": { "return": 200 } } ] }
2021-08-05 16:00:01 +00:00
</para>
</change>
Version bump.
2021-05-28 15:16:23 +00:00
</changes>
Packages: added Ubuntu 21.04 "hirsute" support.
2021-05-27 10:12:52 +00:00
<changes apply="unit-jsc17" ver="1.24.0" rev="1"
Added version 1.24.0 CHANGES.
2021-05-27 13:06:01 +00:00
date="2021-05-27" time="18:00:00 +0300"
Packages: added Ubuntu 21.04 "hirsute" support.
2021-05-27 10:12:52 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Java 17 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-jsc16" ver="1.24.0" rev="1"
Added version 1.24.0 CHANGES.
2021-05-27 13:06:01 +00:00
date="2021-05-27" time="18:00:00 +0300"
Packages: added Ubuntu 21.04 "hirsute" support.
2021-05-27 10:12:52 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Java 16 module for NGINX Unit.
</para>
</change>
</changes>
Version bump.
2021-03-26 08:29:41 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8 unit-python3.9
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11 unit-jsc13
unit-jsc14 unit-jsc15"
ver="1.24.0" rev="1"
Added version 1.24.0 CHANGES.
2021-05-27 13:06:01 +00:00
date="2021-05-27" time="18:00:00 +0300"
Version bump.
2021-03-26 08:29:41 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.24.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.24.0" rev="1"
Added version 1.24.0 CHANGES.
2021-05-27 13:06:01 +00:00
date="2021-05-27" time="18:00:00 +0300"
Version bump.
2021-03-26 08:29:41 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
MIME: added PHP.
2021-05-26 16:48:05 +00:00
<change type="change">
<para>
PHP added to the default MIME type list.
</para>
</change>
Enabling SSL_CTX configuration by using SSL_CONF_cmd(). To perform various configuration operations on SSL_CTX, OpenSSL provides SSL_CONF_cmd(). Specifically, to configure ciphers for a listener, "CipherString" and "Ciphersuites" file commands are used: https://www.openssl.org/docs/man1.1.1/man3/SSL_CONF_cmd.html This feature can be configured in the "tls/conf_commands" section.
2021-05-26 18:19:47 +00:00
<change type="feature">
<para>
arbitrary configuration of TLS connections via OpenSSL commands.
</para>
</change>
Python: support for multiple targets.
2021-05-20 13:02:45 +00:00
<change type="feature">
<para>
Reordered changes for 1.24.0 by significance (subjective).
2021-05-27 13:05:42 +00:00
the ability to limit static file serving by MIME types.
Python: support for multiple targets.
2021-05-20 13:02:45 +00:00
</para>
</change>
Node.js: a shim for overriding "http" and "websocket" modules. Also added stubs for Server.address() This was done to prevent crashes in some popular frameworks like express Supports both CommonJS and the new ES Modules system syntax e.g: app.js: const http = require('http') app.mjs: import http from "http" Usage on Node 14.16.x and higher: { "type": "external", "processes": {"spare": 0}, "working_directory": '/project', "executable": "/usr/bin/env", "arguments": [ "node", "--loader", "unit-http/require_shim.mjs" "--require", "unit-http/require_shim", "app.js" ] } Usage on Node 14.15.x and lower: { "type": "external", "processes": {"spare": 0}, "working_directory": '/project', "executable": "/usr/bin/env", "arguments": [ "node", "--require", "unit-http/require_shim", "app.js" ] }
2021-05-12 09:26:55 +00:00
<change type="feature">
<para>
Reordered changes for 1.24.0 by significance (subjective).
2021-05-27 13:05:42 +00:00
support for chrooting, rejecting symlinks, and rejecting mount
point traversal on a per-request basis when serving static files.
Node.js: a shim for overriding "http" and "websocket" modules. Also added stubs for Server.address() This was done to prevent crashes in some popular frameworks like express Supports both CommonJS and the new ES Modules system syntax e.g: app.js: const http = require('http') app.mjs: import http from "http" Usage on Node 14.16.x and higher: { "type": "external", "processes": {"spare": 0}, "working_directory": '/project', "executable": "/usr/bin/env", "arguments": [ "node", "--loader", "unit-http/require_shim.mjs" "--require", "unit-http/require_shim", "app.js" ] } Usage on Node 14.15.x and lower: { "type": "external", "processes": {"spare": 0}, "working_directory": '/project', "executable": "/usr/bin/env", "arguments": [ "node", "--require", "unit-http/require_shim", "app.js" ] }
2021-05-12 09:26:55 +00:00
</para>
</change>
Static: implemented MIME filtering
2021-05-06 14:22:21 +00:00
<change type="feature">
<para>
Reordered changes for 1.24.0 by significance (subjective).
2021-05-27 13:05:42 +00:00
a loader for automatically overriding the "http" and "websocket" modules in
Node.js.
Static: implemented MIME filtering
2021-05-06 14:22:21 +00:00
</para>
</change>
Static: support for openat2() features. Support for chrooting, rejecting symlinks, and rejecting crossing mounting points on a per-request basis during static file serving.
2021-04-29 14:04:34 +00:00
<change type="feature">
<para>
Reordered changes for 1.24.0 by significance (subjective).
2021-05-27 13:05:42 +00:00
multiple "targets" in Python applications.
Static: support for openat2() features. Support for chrooting, rejecting symlinks, and rejecting crossing mounting points on a per-request basis during static file serving.
2021-04-29 14:04:34 +00:00
</para>
</change>
Ruby: changing deprecated rb_cData to rb_cObject. Ruby 3.0 deprecated rb_cData with the intention to remove it in release 3.1. This commit changes references of rb_cData to rb_cObject. This was done so we can support distributions that package Ruby 3.0, such as Fedora 34. We also need to call rb_undef_alloc_func because we're no longer deriving from rb_cData. This prevents unnecessary allocations. See: https://docs.ruby-lang.org/en/3.0.0/doc/extension_rdoc.html "It is recommended that klass derives from a special class called Data (rb_cData) but not from Object or other ordinal classes. If it doesn't, you have to call rb_undef_alloc_func(klass)."
2021-05-18 10:14:43 +00:00
<change type="feature">
<para>
compatibility with Ruby 3.0.
</para>
</change>
Fixing crash during TLS connection shutdown. A crash was caused by an incorrect timer handler nxt_h1p_idle_timeout() if SSL_shutdown() returned SSL_ERROR_WANT_READ/SSL_ERROR_WANT_WRITE. The flag SSL_RECEIVED_SHUTDOWN is used to avoid getting SSL_ERROR_WANT_READ, so the server won't wait for a close notification from a client. For SSL_ERROR_WANT_WRITE, a correct timer handler is set up.
2021-05-26 18:11:58 +00:00
<change type="bugfix">
<para>
Grammar fixes and improvements in changes.xml.
2021-05-27 12:53:58 +00:00
the router process could crash while closing a TLS connection.
Fixing crash during TLS connection shutdown. A crash was caused by an incorrect timer handler nxt_h1p_idle_timeout() if SSL_shutdown() returned SSL_ERROR_WANT_READ/SSL_ERROR_WANT_WRITE. The flag SSL_RECEIVED_SHUTDOWN is used to avoid getting SSL_ERROR_WANT_READ, so the server won't wait for a close notification from a client. For SSL_ERROR_WANT_WRITE, a correct timer handler is set up.
2021-05-26 18:11:58 +00:00
</para>
</change>
PHP: forced initialization of $_SERVER in fastcgi_finish_request(). The "auto_globals_jit" PHP option postponed the initialization of the $_SERVER global variable until the script using it had been loaded (e. g. via the "include" expression). As a result, nxt_php_register_variables() could be called after fastcgi_finish_request() had finished the request and nulled ctx->req, which thus caused a segmentation fault.
2021-05-07 04:46:25 +00:00
<change type="bugfix">
<para>
a segmentation fault might have occurred in the PHP module if
fastcgi_finish_request() was used with the "auto_globals_jit" option enabled.
</para>
</change>
Version bump.
2021-03-26 08:29:41 +00:00
</changes>
Added version 1.23.0 CHANGES.
2021-03-25 14:14:27 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8 unit-python3.9
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11 unit-jsc13
unit-jsc14 unit-jsc15"
ver="1.23.0" rev="1"
date="2021-03-25" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.23.0.
</para>
</change>
</changes>
Version bump.
2021-02-16 15:54:00 +00:00
<changes apply="unit" ver="1.23.0" rev="1"
Added version 1.23.0 CHANGES.
2021-03-25 14:14:27 +00:00
date="2021-03-25" time="18:00:00 +0300"
Version bump.
2021-02-16 15:54:00 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
Added ability to configure multiple certificates on a listener. The certificate is selected by matching the arriving SNI to the common name and the alternatives names. If no certificate matches the name, the first bundle in the array is chosen.
2021-03-24 20:19:36 +00:00
<change type="feature">
<para>
Fixed wording in docs/changes.xml for the 1.23.0 release.
2021-03-25 14:03:45 +00:00
support for multiple certificate bundles on a listener via the Server Name
Added ability to configure multiple certificates on a listener. The certificate is selected by matching the arriving SNI to the common name and the alternatives names. If no certificate matches the name, the first bundle in the array is chosen.
2021-03-24 20:19:36 +00:00
Indication (SNI) TLS extension.
</para>
</change>
Added build system support for a man page.
2021-03-24 15:45:45 +00:00
<change type="feature">
<para>
Fixed wording in docs/changes.xml for the 1.23.0 release.
2021-03-25 14:03:45 +00:00
"--mandir" ./configure option to specify the directory for man page
installation.
Added build system support for a man page.
2021-03-24 15:45:45 +00:00
</para>
</change>
Fixed TLS connection shutdown on errors. An immediate return statement on connection errors was mistakenly added to the beginning of nxt_openssl_conn_io_shutdown() in ecd3c5bbf7d8, breaking the TLS connection finalization procedure. As a result, a TLS connection was left unfinalized if it had been closed prematurely or a fatal protocol error had occurred, which caused memory and socket descriptor leakage. Moreover, in some cases (notably, on handshake errors in tests with kqueue on macOS) the read event was triggered later and nxt_h1p_conn_error() was called the second time; after the change in af93c866b4f0, the latter call crashed the router process in an attempt to remove a connection from the idle queue twice.
2021-03-15 11:57:01 +00:00
<change type="bugfix">
<para>
the router process could crash on premature TLS connection close; the bug had
appeared in 1.17.0.
</para>
</change>
<change type="bugfix">
<para>
Fixed wording in docs/changes.xml for the 1.23.0 release.
2021-03-25 14:03:45 +00:00
a connection leak occurred on premature TLS connection close; the bug had
Fixed TLS connection shutdown on errors. An immediate return statement on connection errors was mistakenly added to the beginning of nxt_openssl_conn_io_shutdown() in ecd3c5bbf7d8, breaking the TLS connection finalization procedure. As a result, a TLS connection was left unfinalized if it had been closed prematurely or a fatal protocol error had occurred, which caused memory and socket descriptor leakage. Moreover, in some cases (notably, on handshake errors in tests with kqueue on macOS) the read event was triggered later and nxt_h1p_conn_error() was called the second time; after the change in af93c866b4f0, the latter call crashed the router process in an attempt to remove a connection from the idle queue twice.
2021-03-15 11:57:01 +00:00
appeared in 1.6.
</para>
</change>
Fixing shm buffer leakage when sending over the port queue. When the shm buffer is sent over the port queue, it needs to be completed because it's sent over the port socket.
2021-03-25 13:55:16 +00:00
<change type="bugfix">
<para>
Fixed wording in docs/changes.xml for the 1.23.0 release.
2021-03-25 14:03:45 +00:00
a descriptor and memory leak occurred in the router process when processing
Fixing shm buffer leakage when sending over the port queue. When the shm buffer is sent over the port queue, it needs to be completed because it's sent over the port socket.
2021-03-25 13:55:16 +00:00
small WebSocket frames from a client; the bug had appeared in 1.19.0.
</para>
</change>
Closing app outgoing shared memory file descriptor. This fixes file descriptor leakage in router. Shared memory file used to send data from router to application. These files are shared among all processes of same application and router keeps the opened file descriptor since 06017e6e3a5f commit.
2021-03-02 16:33:37 +00:00
<change type="bugfix">
<para>
Fixed wording in docs/changes.xml for the 1.23.0 release.
2021-03-25 14:03:45 +00:00
a descriptor leak occurred in the router process when removing or
Closing app outgoing shared memory file descriptor. This fixes file descriptor leakage in router. Shared memory file used to send data from router to application. These files are shared among all processes of same application and router keeps the opened file descriptor since 06017e6e3a5f commit.
2021-03-02 16:33:37 +00:00
reconfiguring an application; the bug had appeared in 1.19.0.
</para>
</change>
Version bump.
2021-02-16 15:54:00 +00:00
Fixed certificates loading on startup with some filesystems. It appears that readdir() on Linux detects file types unreliably, always setting the "d_type" field to DT_UNKNOWN for some less common filesystems. As a result, all files were skipped and no certificate bundles were found when the state directory was located on such filesystems. Skipping "." and ".." instead of any non-regular files should be enough, as no other non-regular files normally appear in this directory. This closes #368 issue on GitHub.
2021-03-15 11:57:31 +00:00
<change type="bugfix">
<para>
persistent storage of certificates might've not worked with some filesystems in
Linux, and all uploaded certificate bundles were forgotten after restart.
</para>
</change>
Certficates: fixed counting DNS SAN entries. Previously, entries of any type were counted during object allocation but only DNS type entries were actually processed. As a result, if some certificate entries had another type, returning information about the certificate caused uninitialized memory access.
2021-03-24 13:38:05 +00:00
<change type="bugfix">
<para>
the controller process could crash while requesting information about a
certificate with a non-DNS SAN entry.
</para>
</change>
Certificates: fixed in name attributes processing. The idea is to put SAN after CN, but the previous version of the code incorrectly assumed that CN was always present, which caused writes outside the allocated object if there were no standard name attributes.
2021-03-24 13:55:47 +00:00
<change type="bugfix">
<para>
the controller process could crash on manipulations with a certificate
Fixed wording in docs/changes.xml for the 1.23.0 release.
2021-03-25 14:03:45 +00:00
containing a SAN and no standard name attributes in subject or issuer.
Certificates: fixed in name attributes processing. The idea is to put SAN after CN, but the previous version of the code incorrectly assumed that CN was always present, which caused writes outside the allocated object if there were no standard name attributes.
2021-03-24 13:55:47 +00:00
</para>
</change>
Ruby: fixed encodings initialization. The Ruby interpreter expects an explicit setlocale() call before initialization to pick up character encodings in the "Encoding" class from the environment. This closes #531 issue on GitHub.
2021-03-15 12:03:32 +00:00
<change type="bugfix">
<para>
Fixed wording in docs/changes.xml for the 1.23.0 release.
2021-03-25 14:03:45 +00:00
the Ruby module didn't respect the user locale for defaults in the Encoding
class.
Ruby: fixed encodings initialization. The Ruby interpreter expects an explicit setlocale() call before initialization to pick up character encodings in the "Encoding" class from the environment. This closes #531 issue on GitHub.
2021-03-15 12:03:32 +00:00
</para>
</change>
Fixed building the PHP 5 module with ZTS, broken by dab8544b5440. This closes #525 issue on GitHub.
2021-03-15 12:03:32 +00:00
<change type="bugfix">
<para>
the PHP 5 module failed to build with thread safety enabled; the bug had
appeared in 1.22.0.
</para>
</change>
Version bump.
2021-02-16 15:54:00 +00:00
</changes>
Added changelog for Python 3.9 module appeared for Fedora 33.
2021-02-04 15:48:59 +00:00
<changes apply="unit-python3.9" ver="1.22.0" rev="1"
date="2021-02-04" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Python 3.9 module for NGINX Unit.
</para>
</change>
</changes>
Version bump for unit modules. This is required in order to build Debian packages from current tip without making manual interventions. Moving forward, this should be a part of every version bump commit.
2020-12-24 12:18:49 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11 unit-jsc13
unit-jsc14 unit-jsc15"
ver="1.22.0" rev="1"
Added version 1.22.0 CHANGES.
2021-02-04 15:22:33 +00:00
date="2021-02-04" time="18:00:00 +0300"
Version bump for unit modules. This is required in order to build Debian packages from current tip without making manual interventions. Moving forward, this should be a part of every version bump commit.
2020-12-24 12:18:49 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.22.0.
</para>
</change>
</changes>
Version bump.
2020-11-24 13:40:28 +00:00
<changes apply="unit" ver="1.22.0" rev="1"
Added version 1.22.0 CHANGES.
2021-02-04 15:22:33 +00:00
date="2021-02-04" time="18:00:00 +0300"
Version bump.
2020-11-24 13:40:28 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
Python: multiple values in the "path" option.
2020-12-22 14:53:41 +00:00
<change type="feature">
<para>
Reordered changes for 1.22.0 by significance (subjective).
2021-02-04 15:22:33 +00:00
the ServerRequest and ServerResponse objects of Node.js module are now
compliant with Stream API.
Python: multiple values in the "path" option.
2020-12-22 14:53:41 +00:00
</para>
</change>
Node.js: ServerRequest and ServerResponse compliance to Stream API. ServerRequest now inherit stream Readable object. ServerResponse provides 'writable' property. Thanks to Wu Jian Ping (@wujjpp). This closes #274, closes #317 issues and closes #502 PR on GitHub.
2020-12-29 16:00:54 +00:00
<change type="feature">
<para>
Reordered changes for 1.22.0 by significance (subjective).
2021-02-04 15:22:33 +00:00
support for specifying multiple directories in the "path" option of Python
apps.
Node.js: ServerRequest and ServerResponse compliance to Stream API. ServerRequest now inherit stream Readable object. ServerResponse provides 'writable' property. Thanks to Wu Jian Ping (@wujjpp). This closes #274, closes #317 issues and closes #502 PR on GitHub.
2020-12-29 16:00:54 +00:00
</para>
</change>
HTTP: fixed status line format for unknown status codes. According to Section #3.1.2 of RFC 7230, after the status code there must be a space even if the reason phrase is empty. Also, only 3 digits allowed. This closes #507 issue on GitHub.
2020-12-07 15:50:56 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.22.0 by significance (subjective).
2021-02-04 15:22:33 +00:00
a memory leak occurred in the router process when serving files larger than
128K; the bug had appeared in 1.13.0.
HTTP: fixed status line format for unknown status codes. According to Section #3.1.2 of RFC 7230, after the status code there must be a space even if the reason phrase is empty. Also, only 3 digits allowed. This closes #507 issue on GitHub.
2020-12-07 15:50:56 +00:00
</para>
</change>
PHP: populating PHP_AUTH_* server variables. This closes #498 issue on GitHub.
2020-12-07 22:59:46 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.22.0 by significance (subjective).
2021-02-04 15:22:33 +00:00
apps could stop processing new requests under high load; the bug had
appeared in 1.19.0.
PHP: populating PHP_AUTH_* server variables. This closes #498 issue on GitHub.
2020-12-07 22:59:46 +00:00
</para>
</change>
Ruby: fixed crash on thread start. Ruby threads need to be created with GVL; otherwise, an attempt to access locked resources may occur, causing a crash. The issue was occasionally reproduced on Ubuntu 18.04 with Ruby 2.5.1 while running test_ruby_application_threads.
2020-12-07 18:17:25 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.22.0 by significance (subjective).
2021-02-04 15:22:33 +00:00
app processes could terminate unexpectedly under high load; the bug had
appeared in 1.19.0.
Ruby: fixed crash on thread start. Ruby threads need to be created with GVL; otherwise, an attempt to access locked resources may occur, causing a crash. The issue was occasionally reproduced on Ubuntu 18.04 with Ruby 2.5.1 while running test_ruby_application_threads.
2020-12-07 18:17:25 +00:00
</para>
</change>
Added a changelog for 5e6c2b8fb3fe.
2020-12-15 13:01:44 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.22.0 by significance (subjective).
2021-02-04 15:22:33 +00:00
invalid HTTP responses were generated for some unusual status codes.
Added a changelog for 5e6c2b8fb3fe.
2020-12-15 13:01:44 +00:00
</para>
</change>
Router: fixed crash in OOSM processing. Multithreaded application may create different shared memory segments in different threads. The segments then passed to different router threads. Because of this multithreading, the order of adding incoming segments is not determined and there can be situation when some of the incoming segments are not initialized yet. This patch simply adds check for NULL to skip non-initialized segments. Crash reproduced during load tests with high number of simultaneous connections (1024 and more).
2020-12-17 16:27:44 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.22.0 by significance (subjective).
2021-02-04 15:22:33 +00:00
the PHP_AUTH_USER, PHP_AUTH_PW, and PHP_AUTH_DIGEST server variables were
missing in the PHP module.
Router: fixed crash in OOSM processing. Multithreaded application may create different shared memory segments in different threads. The segments then passed to different router threads. Because of this multithreading, the order of adding incoming segments is not determined and there can be situation when some of the incoming segments are not initialized yet. This patch simply adds check for NULL to skip non-initialized segments. Crash reproduced during load tests with high number of simultaneous connections (1024 and more).
2020-12-17 16:27:44 +00:00
</para>
</change>
Limiting app queue notifications count in socket. Under high load, a queue synchonization issue may occur, starting from the steady state when an app queue message is dequeued immediately after it has been enqueued. In this state, the router always puts the first message in the queue and is forced to notify the app about a new message in an empty queue using a socket pair. On the other hand, the application dequeues and processes the message without reading the notification from the socket, so the socket buffer overflows with notifications. The issue was reproduced during Unit load tests. After a socket buffer overflow, the router is unable to notify the app about a new first message. When another message is enqueued, a notification is not required, so the queue grows without being read by the app. As a result, request processing stops. This patch changes the notification algorithm by counting the notifications in the pipe instead of getting the number of messages in the queue.
2020-12-17 21:25:27 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.22.0 by significance (subjective).
2021-02-04 15:22:33 +00:00
the router process could crash with multithreaded apps under high load.
Limiting app queue notifications count in socket. Under high load, a queue synchonization issue may occur, starting from the steady state when an app queue message is dequeued immediately after it has been enqueued. In this state, the router always puts the first message in the queue and is forced to notify the app about a new message in an empty queue using a socket pair. On the other hand, the application dequeues and processes the message without reading the notification from the socket, so the socket buffer overflows with notifications. The issue was reproduced during Unit load tests. After a socket buffer overflow, the router is unable to notify the app about a new first message. When another message is enqueued, a notification is not required, so the queue grows without being read by the app. As a result, request processing stops. This patch changes the notification algorithm by counting the notifications in the pipe instead of getting the number of messages in the queue.
2020-12-17 21:25:27 +00:00
</para>
</change>
Libunit: fixed shared memory waiting. The nxt_unit_ctx_port_recv() function may return the NXT_UNIT_AGAIN code, in which case an attempt to reread the message should be made. The issue was reproduced in load testing with response sizes 16k and up. In the rare case of a NXT_UNIT_AGAIN result, a buffer of size -1 was processed, which triggered a 'message too small' alert; after that, the app process was terminated.
2020-12-17 21:25:28 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.22.0 by significance (subjective).
2021-02-04 15:22:33 +00:00
Ruby apps with multithreading configured could crash on start under load.
Libunit: fixed shared memory waiting. The nxt_unit_ctx_port_recv() function may return the NXT_UNIT_AGAIN code, in which case an attempt to reread the message should be made. The issue was reproduced in load testing with response sizes 16k and up. In the rare case of a NXT_UNIT_AGAIN result, a buffer of size -1 was processed, which triggered a 'message too small' alert; after that, the app process was terminated.
2020-12-17 21:25:28 +00:00
</para>
</change>
Static: fixing request memory pool leakage in router. When a static file larger than NXT_HTTP_STATIC_BUF_SIZE (128K) is served, two buffers are allocated and chained; each retains the whole request memory pool. Starting from 41331471eee7, the completion handler was called once for a linked buffer chain, but the second buffer got lost. This patch improves the completion handler's treatment of static buffers to handle all linked buffers.
2020-12-23 08:01:36 +00:00
<change type="bugfix">
<para>
Reordered changes for 1.22.0 by significance (subjective).
2021-02-04 15:22:33 +00:00
mount points weren't unmounted when the "mount" namespace isolation was used;
the bug had appeared in 1.21.0.
Static: fixing request memory pool leakage in router. When a static file larger than NXT_HTTP_STATIC_BUF_SIZE (128K) is served, two buffers are allocated and chained; each retains the whole request memory pool. Starting from 41331471eee7, the completion handler was called once for a linked buffer chain, but the second buffer got lost. This patch improves the completion handler's treatment of static buffers to handle all linked buffers.
2020-12-23 08:01:36 +00:00
</para>
</change>
Router: fixing crash after WebSocket processing. After WebSocket processing, the application port was released with incorrect reason ("got request"), unnecessarily decrementing the active request counter. The assertion was triggered only on application removal; a test was added for this case.
2021-01-28 14:13:52 +00:00
<change type="bugfix">
<para>
Updated phrasing and corrected errors in docs/changes.xml.
2021-02-04 14:34:42 +00:00
the router process could crash while removing or reconfiguring an app that used
WebSocket.
Router: fixing crash after WebSocket processing. After WebSocket processing, the application port was released with incorrect reason ("got request"), unnecessarily decrementing the active request counter. The assertion was triggered only on application removal; a test was added for this case.
2021-01-28 14:13:52 +00:00
</para>
</change>
Fixing shared app queue unmap size. Shared app queue takes more memory than port memory. To unmap all memory pages correct size need to be specified for munmap() call. Otherwise 4 Mb memory leaked on each configured application removal. The issue was introduced in 1d84b9e4b459.
2021-02-03 20:23:28 +00:00
<change type="bugfix">
<para>
a memory leak occurring in the router process when removing or reconfiguring
an application; the bug had appeared in 1.19.0.
</para>
</change>
Version bump.
2020-11-24 13:40:28 +00:00
</changes>
Added version 1.21.0 CHANGES.
2020-11-19 16:59:18 +00:00
<changes apply="unit-jsc15" ver="1.21.0" rev="1"
date="2020-11-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Java 15 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-jsc14" ver="1.21.0" rev="1"
date="2020-11-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Java 14 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-jsc13" ver="1.21.0" rev="1"
date="2020-11-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Java 13 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.21.0" rev="1"
date="2020-11-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.21.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.21.0" rev="1"
date="2020-11-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="change">
<para>
procfs is mounted by default for all languages when "rootfs" isolation is used.
</para>
</change>
<change type="change">
<para>
any characters valid according to RFC 7230 are now allowed in HTTP header field
names.
</para>
</change>
<change type="change">
<para>
HTTP header fields with underscores ("_") are now discarded from requests by
default.
</para>
</change>
<change type="feature">
<para>
optional multithreaded request processing for Java, Python, Perl, and Ruby apps.
</para>
</change>
<change type="feature">
<para>
regular expressions in route matching patterns.
</para>
</change>
<change type="feature">
<para>
compatibility with Python 3.9.
</para>
</change>
<change type="feature">
<para>
the Python module now supports ASGI 2.0 legacy applications.
</para>
</change>
<change type="feature">
<para>
the "protocol" option in Python applications aids choice between ASGI and WSGI.
</para>
</change>
<change type="feature">
<para>
the fastcgi_finish_request() PHP function that finalizes request processing and
continues code execution without holding onto the client connection.
</para>
</change>
<change type="feature">
<para>
the "discard_unsafe_fields" HTTP option that enables discarding request header
fields with irregular (but still valid) characters in the field name.
</para>
</change>
<change type="feature">
<para>
the "procfs" and "tmpfs" automount isolation options to disable automatic
mounting of eponymous filesystems.
</para>
</change>
<change type="bugfix">
<para>
the router process could crash when running Go applications under high load;
the bug had appeared in 1.19.0.
</para>
</change>
<change type="bugfix">
<para>
some language dependencies could remain mounted after using "rootfs" isolation.
</para>
</change>
<change type="bugfix">
<para>
various compatibility issues in Java applications.
</para>
</change>
<change type="bugfix">
<para>
the Java module built with the musl C library couldn't run applications that
use "rootfs" isolation.
</para>
</change>
</changes>
Added version 1.20.0 CHANGES.
2020-10-08 15:32:36 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.20.0" rev="1"
date="2020-10-08" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.20.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.20.0" rev="1"
date="2020-10-08" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="change">
<para>
the PHP module is now initialized before chrooting; this enables loading all
extensions from the host system.
</para>
</change>
<change type="change">
<para>
AVIF and APNG image formats added to the default MIME type list.
</para>
</change>
Updated 1.20.0 CHANGES to include pytest migration.
2020-10-08 16:04:40 +00:00
<change type="change">
<para>
functional tests migrated to the pytest framework.
</para>
</change>
Added version 1.20.0 CHANGES.
2020-10-08 15:32:36 +00:00
<change type="feature">
<para>
the Python module now fully supports applications that use the ASGI 3.0 server
interface.
</para>
</change>
<change type="feature">
<para>
the Python module now has a built-in WebSocket server implementation for
applications, compatible with the HTTP &amp; WebSocket ASGI Message Format 2.1
specification.
</para>
</change>
<change type="feature">
<para>
automatic mounting of an isolated "/tmp" file system into chrooted application
environments.
</para>
</change>
<change type="feature">
<para>
the $host variable contains a normalized "Host" request value.
</para>
</change>
<change type="feature">
<para>
the "callable" option sets Python application callable names.
</para>
</change>
<change type="feature">
<para>
compatibility with PHP 8 RC 1. Thanks to Remi Collet.
</para>
</change>
<change type="feature">
<para>
the "automount" option in the "isolation" object allows to turn off the
automatic mounting of language module dependencies.
</para>
</change>
<change type="bugfix">
<para>
"pass"-ing requests to upstreams from a route was broken; the bug had appeared
in 1.19.0. Thanks to 洪志道 (Hong Zhi Dao) for discovering and fixing it.
</para>
</change>
<change type="bugfix">
<para>
the router process could crash during reconfiguration.
</para>
</change>
<change type="bugfix">
<para>
a memory leak occurring in the router process; the bug had appeared in 1.18.0.
</para>
</change>
<change type="bugfix">
<para>
the "!" (non-empty) pattern was matched incorrectly;
the bug had appeared in 1.19.0.
</para>
</change>
<change type="bugfix">
<para>
fixed building on platforms without sendfile() support, notably NetBSD;
the bug had appeared in 1.16.0.
</para>
</change>
</changes>
Added version 1.19.0 CHANGES.
2020-08-13 16:22:41 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.19.0" rev="1"
date="2020-08-13" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.19.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.19.0" rev="1"
date="2020-08-13" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="feature">
<para>
reworked IPC between the router process and the applications to lower latencies,
increase performance, and improve scalability.
</para>
</change>
<change type="feature">
<para>
support for an arbitrary number of wildcards in route matching patterns.
</para>
</change>
<change type="feature">
<para>
chunked transfer encoding in proxy responses.
</para>
</change>
<change type="feature">
<para>
basic variables support in the "pass" option.
</para>
</change>
<change type="feature">
<para>
compatibility with PHP 8 Beta 1.
Thanks to Remi Collet.
</para>
</change>
<change type="bugfix">
<para>
the router process could crash while passing requests to an application under
high load.
</para>
</change>
<change type="bugfix">
<para>
a number of language modules failed to build on some systems;
the bug had appeared in 1.18.0.
</para>
</change>
<change type="bugfix">
<para>
time in error log messages from PHP applications could lag.
</para>
</change>
<change type="bugfix">
<para>
reconfiguration requests could hang if an application had failed to start;
the bug had appeared in 1.18.0.
</para>
</change>
<change type="bugfix">
<para>
memory leak during reconfiguration.
</para>
</change>
<change type="bugfix">
<para>
the daemon didn't start without language modules;
the bug had appeared in 1.18.0.
</para>
</change>
<change type="bugfix">
<para>
the router process could crash at exit.
</para>
</change>
<change type="bugfix">
<para>
Node.js applications could crash at exit.
</para>
</change>
<change type="bugfix">
<para>
the Ruby module could be linked against a wrong library version.
</para>
</change>
</changes>
Added version 1.18.0 CHANGES.
2020-05-28 14:34:06 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.18.0" rev="1"
date="2020-05-28" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.18.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.18.0" rev="1"
date="2020-05-28" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="feature">
<para>
the "rootfs" isolation option for changing root filesystem for an application.
</para>
</change>
<change type="feature">
<para>
multiple "targets" in PHP applications.
</para>
</change>
<change type="feature">
<para>
support for percent-encoding in the "uri" and "arguments" matching options
and in the "pass" option.
</para>
</change>
</changes>
Added version 1.17.0 CHANGES.
2020-04-16 14:49:09 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.17.0" rev="1"
date="2020-04-16" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.17.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.17.0" rev="1"
date="2020-04-16" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="feature">
<para>
a "return" action with optional "location" for immediate responses and external
redirection.
</para>
</change>
<change type="feature">
<para>
fractional weights support for upstream servers.
</para>
</change>
<change type="bugfix">
<para>
accidental 502 "Bad Gateway" errors might have occurred in applications under
high load.
</para>
</change>
<change type="bugfix">
<para>
memory leak in the router; the bug had appeared in 1.13.0.
</para>
</change>
<change type="bugfix">
<para>
segmentation fault might have occurred in the router process when reaching
open connections limit.
</para>
</change>
<change type="bugfix">
<para>
"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.
</para>
</change>
<change type="bugfix">
<para>
existing application processes didn't reopen the log file.
</para>
</change>
<change type="bugfix">
<para>
incompatibility with some Node.js applications.
</para>
</change>
<change type="bugfix">
<para>
broken build on DragonFly BSD; the bug had appeared in 1.16.0.
</para>
</change>
</changes>
Added version 1.16.0 CHANGES.
2020-03-12 15:13:07 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.16.0" rev="1"
date="2020-03-12" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.16.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.16.0" rev="1"
date="2020-03-12" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="feature">
<para>
basic load-balancing support with round-robin.
</para>
</change>
<change type="feature">
<para>
a "fallback" option that performs an alternative action if a request can't be
served from the "share" directory.
</para>
</change>
<change type="feature">
<para>
reduced memory consumption by dumping large request bodies to disk.
</para>
</change>
<change type="feature">
<para>
stripping UTF-8 BOM and JavaScript-style comments from uploaded JSON.
</para>
</change>
<change type="bugfix">
<para>
negative address matching in router might work improperly in combination with
non-negative patterns.
</para>
</change>
<change type="bugfix">
<para>
Java Spring applications failed to run; the bug had appeared in 1.10.0.
</para>
</change>
<change type="bugfix">
<para>
PHP 7.4 was broken if it was built with thread safety enabled.
</para>
</change>
<change type="bugfix">
<para>
compatibility issues with some Python applications.
</para>
</change>
</changes>
Added version 1.15.0 CHANGES.
2020-02-06 14:33:44 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.15.0" rev="1"
date="2020-02-06" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.15.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.15.0" rev="1"
date="2020-02-06" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="change">
<para>
extensions of dynamically requested PHP scripts were restricted to ".php".
</para>
</change>
<change type="feature">
<para>
compatibility with Ruby 2.7.
</para>
</change>
<change type="bugfix">
<para>
segmentation fault might have occurred in the router process with multiple
application processes under load; the bug had appeared in 1.14.0.
</para>
</change>
<change type="bugfix">
<para>
receiving request body over TLS connection might have stalled.
</para>
</change>
</changes>
Added version 1.14.0 CHANGES.
2019-12-26 14:03:21 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-python3.8
unit-go
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.14.0" rev="1"
date="2019-12-26" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.14.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.14.0" rev="1"
date="2019-12-26" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="change">
<para>
the Go package import name changed to "unit.nginx.org/go".
</para>
</change>
<change type="change">
<para>
Go package now links to libunit instead of including library sources.
</para>
</change>
<change type="feature">
<para>
ability to change user and group for isolated applications when Unit daemon
runs as an unprivileged user.
</para>
</change>
<change type="feature">
<para>
request routing by source and destination addresses and ports.
</para>
</change>
<change type="bugfix">
<para>
memory bloat on large responses.
</para>
</change>
</changes>
Packages: added Ubuntu 19.10 "eoan" support.
2019-11-21 11:13:24 +00:00
<changes apply="unit-go1.13" ver="1.13.0" rev="1"
date="2019-11-20" time="09:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Go 1.13 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-go1.12" ver="1.13.0" rev="1"
date="2019-11-20" time="09:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Go 1.12 module for NGINX Unit.
</para>
</change>
</changes>
Packages: added Python 3.8 on Ubuntu 18.04, 19.04.
2019-11-19 09:43:51 +00:00
<changes apply="unit-python3.8" ver="1.13.0" rev="1"
date="2019-11-18" time="14:20:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Python 3.8 module for NGINX Unit.
</para>
</change>
</changes>
Added version 1.13.0 CHANGES.
2019-11-14 16:23:38 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10 unit-go1.11
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.13.0" rev="1"
date="2019-11-14" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.13.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.13.0" rev="1"
date="2019-11-14" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="feature">
<para>
basic support for HTTP reverse proxying.
</para>
</change>
<change type="feature">
<para>
compatibility with Python 3.8.
</para>
</change>
<change type="bugfix">
<para>
memory leak in Python application processes when the close handler was used.
</para>
</change>
<change type="bugfix">
<para>
threads in Python applications might not work correctly.
</para>
</change>
<change type="bugfix">
<para>
Ruby on Rails applications might not work on Ruby 2.6.
</para>
</change>
<change type="bugfix">
<para>
backtraces for uncaught exceptions in Python 3 might be logged with significant
delays.
</para>
</change>
<change type="bugfix">
<para>
explicit setting a namespaces isolation option to false might have enabled it.
</para>
</change>
</changes>
Added version 1.12.0 CHANGES.
2019-10-03 13:30:31 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10 unit-go1.11
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.12.0" rev="1"
date="2019-10-03" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.12.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.12.0" rev="1"
date="2019-10-03" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="feature">
<para>
compatibility with PHP 7.4.
</para>
</change>
<change type="bugfix">
<para>
descriptors leak on process creation; the bug had appeared in 1.11.0.
</para>
</change>
<change type="bugfix">
<para>
TLS connection might be closed prematurely while sending response.
</para>
</change>
<change type="bugfix">
<para>
segmentation fault might have occurred if an irregular file was requested.
</para>
</change>
</changes>
Added version 1.11.0 CHANGES.
2019-09-19 14:28:55 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10 unit-go1.11
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.11.0" rev="1"
date="2019-09-19" time="18:00:00 +0300"
packager="Konstantin Pavlov &lt;thresh@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.11.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.11.0" rev="1"
date="2019-09-19" time="18:00:00 +0300"
packager="Konstantin Pavlov &lt;thresh@nginx.com&gt;">
<change type="feature">
<para>
basic support for serving static files.
</para>
</change>
<change type="feature">
<para>
isolation of application processes with Linux namespaces.
</para>
</change>
<change type="feature">
<para>
built-in WebSocket server implementation for Java Servlet Containers.
</para>
</change>
<change type="feature">
<para>
direct addressing of API configuration options containing slashes "/"
using URI encoding (%2F).
</para>
</change>
<change type="bugfix">
<para>
segmentation fault might have occurred in Go applications under high load.
</para>
</change>
<change type="bugfix">
<para>
WebSocket support was broken if Unit was built with some linkers other than
GNU ld (e.g. gold or LLD).
</para>
</change>
</changes>
Added changes for 1.10.0-2 bugfix release.
2019-08-23 09:10:20 +00:00
<changes apply="unit
unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10 unit-go1.11
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.10.0" rev="2"
date="2019-08-23" time="12:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="bugfix">
<para>
missed header files added to unit development package.
</para>
</change>
</changes>
Added version 1.10.0 CHANGES.
2019-08-22 15:43:02 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10 unit-go1.11
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.10.0" rev="1"
date="2019-08-22" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.10.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.10.0" rev="1"
date="2019-08-22" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="change">
<para>
matching of cookies in routes made case sensitive.
</para>
</change>
<change type="change">
<para>
decreased log level of common errors when clients close connections.
</para>
</change>
<change type="change">
<para>
removed the Perl module's "--include=" ./configure option.
</para>
</change>
<change type="feature">
<para>
built-in WebSocket server implementation for Node.js module.
</para>
</change>
<change type="feature">
<para>
splitting PATH_INFO from request URI in PHP module.
</para>
</change>
<change type="feature">
<para>
request routing by scheme (HTTP or HTTPS).
</para>
</change>
<change type="feature">
<para>
support for multipart requests body in Java module.
</para>
</change>
<change type="feature">
<para>
improved API compatibility with Node.js 11.10 or later.
</para>
</change>
<change type="bugfix">
<para>
reconfiguration failed if "listeners" or "applications" objects were missing.
</para>
</change>
<change type="bugfix">
<para>
applying a large configuration might have failed.
</para>
</change>
</changes>
Added version 1.9 CHANGES.
2019-05-30 14:16:23 +00:00
<changes apply="unit-go1.11" ver="1.9.0" rev="1"
date="2019-05-30" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Go 1.11 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10
unit-perl
unit-ruby
unit-jsc-common unit-jsc8 unit-jsc10 unit-jsc11"
ver="1.9.0" rev="1"
date="2019-05-30" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.9.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.9.0" rev="1"
date="2019-05-30" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="feature">
<para>
request routing by arguments, headers, and cookies.
</para>
</change>
<change type="feature">
<para>
route matching patterns allow a wildcard in the middle.
</para>
</change>
<change type="feature">
<para>
POST operation for appending elements to arrays in configuration.
</para>
</change>
<change type="feature">
<para>
support for changing credentials using CAP_SETUID and CAP_SETGID capabilities
on Linux without running main process as privileged user.
</para>
</change>
<change type="bugfix">
<para>
memory leak in the router process might have happened when a client
prematurely closed the connection.
</para>
</change>
<change type="bugfix">
<para>
applying a large configuration might have failed.
</para>
</change>
<change type="bugfix">
<para>
PUT and DELETE operations on array elements in configuration did not work.
</para>
</change>
<change type="bugfix">
<para>
request schema in applications did not reflect TLS connections.
</para>
</change>
<change type="bugfix">
<para>
restored compatibility with Node.js applications that use
ServerResponse._implicitHeader() function; the bug had appeared in 1.7.
</para>
</change>
<change type="bugfix">
<para>
various compatibility issues with Node.js applications.
</para>
</change>
</changes>
Added version 1.8.0 CHANGES.
2019-03-01 15:23:38 +00:00
<changes apply="unit-jsc-common" ver="1.8.0" rev="1"
date="2019-03-01" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Java common packages for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-jsc8" ver="1.8.0" rev="1"
date="2019-03-01" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Java 8 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-jsc10" ver="1.8.0" rev="1"
date="2019-03-01" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Java 10 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-jsc11" ver="1.8.0" rev="1"
date="2019-03-01" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Java 11 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10
unit-perl
unit-ruby"
ver="1.8.0" rev="1"
date="2019-03-01" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.8.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.8.0" rev="1"
date="2019-03-01" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="change">
<para>
now three numbers are always used for versioning: major, minor,
and patch versions.
</para>
</change>
<change type="change">
<para>
now QUERY_STRING is always defined even if the request does not include
the query component.
</para>
</change>
<change type="feature">
<para>
basic internal request routing by Host, URI, and method.
</para>
</change>
<change type="feature">
<para>
experimental support for Java Servlet Containers.
</para>
</change>
<change type="bugfix">
<para>
segmentation fault might have occurred in the router process.
</para>
</change>
<change type="bugfix">
<para>
various potential memory leaks.
</para>
</change>
<change type="bugfix">
<para>
TLS connections might have stalled.
</para>
</change>
<change type="bugfix">
<para>
some Perl applications might have failed to send the response body.
</para>
</change>
<change type="bugfix">
<para>
some compilers with specific flags might have produced non-functioning builds;
the bug had appeared in 1.5.
</para>
</change>
<change type="bugfix">
<para>
Node.js package had wrong version number when installed from sources.
</para>
</change>
</changes>
Added version 1.7.1 CHANGES.
2019-02-07 14:46:46 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6 unit-python3.7
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10
unit-perl
unit-ruby"
ver="1.7.1" rev="1"
date="2019-02-07" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.7.1.
</para>
</change>
</changes>
<changes apply="unit" ver="1.7.1" rev="1"
date="2019-02-07" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="security">
<para>
a heap memory buffer overflow might have been caused in the router process by
a specially crafted request, potentially resulting in a segmentation fault or
other unspecified behavior (CVE-2019-7401).
</para>
</change>
<change type="bugfix">
<para>
install of Go module failed without prior building of Unit daemon;
the bug had appeared in 1.7.
</para>
</change>
</changes>
Packages: Ubuntu 18.10 "cosmic" support added.
2018-12-27 08:07:24 +00:00
<changes apply="unit-python3.7" ver="1.7" rev="1"
date="2018-12-25" time="10:30:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Python 3.7 module for NGINX Unit.
</para>
</change>
</changes>
Added version 1.7 CHANGES.
2018-12-20 16:17:08 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10
unit-perl
unit-ruby"
ver="1.7" rev="1"
date="2018-12-20" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.7.
</para>
</change>
</changes>
<changes apply="unit" ver="1.7" rev="1"
date="2018-12-20" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="change">
<para>
now rpath is set in Ruby module only if the library was not found in default
search paths; this allows to meet packaging restrictions on some systems.
</para>
</change>
<change type="bugfix">
<para>
"disable_functions" and "disable_classes" PHP options set via Control API
did not work.
</para>
</change>
<change type="bugfix">
<para>
Promises on request data in Node.js were not triggered.
</para>
</change>
<change type="bugfix">
<para>
various compatibility issues with Node.js applications.
</para>
</change>
<change type="bugfix">
<para>
a segmentation fault occurred in Node.js module if application tried to read
request body after request.end() was called.
</para>
</change>
<change type="bugfix">
<para>
a segmentation fault occurred in Node.js module if application attempted to
send header twice.
</para>
</change>
<change type="bugfix">
<para>
names of response header fields in Node.js module were erroneously treated as
case-sensitive.
</para>
</change>
<change type="bugfix">
<para>
uncatched exceptions in Node.js were not logged.
</para>
</change>
<change type="bugfix">
<para>
global install of Node.js module from sources was broken on some systems;
the bug had appeared in 1.6.
</para>
</change>
<change type="bugfix">
<para>
traceback for exceptions during initialization of Python applications might not
be logged.
</para>
</change>
<change type="bugfix">
<para>
PHP module build failed if PHP interpreter was built with thread safety
enabled.
</para>
</change>
</changes>
Added version 1.6 CHANGES.
2018-11-15 12:56:09 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10
unit-perl
unit-ruby"
ver="1.6" rev="1"
date="2018-11-15" time="18:00:00 +0300"
packager="Konstantin Pavlov &lt;thresh@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.6.
</para>
</change>
</changes>
<changes apply="unit" ver="1.6" rev="1"
date="2018-11-15" time="18:00:00 +0300"
packager="Konstantin Pavlov &lt;thresh@nginx.com&gt;">
<change type="change">
<para>
"make install" now installs Node.js module as well if it was configured.
</para>
</change>
<change type="feature">
<para>
"--local" ./configure option to install Node.js module locally.
</para>
</change>
<change type="bugfix">
<para>
Node.js module might have crashed due to broken reference counting.
</para>
</change>
<change type="bugfix">
<para>
asynchronous operations in Node.js might not have worked.
</para>
</change>
<change type="bugfix">
<para>
various compatibility issues with Node.js applications.
</para>
</change>
<change type="bugfix">
<para>
"freed pointer is out of pool" alerts might have appeared in log.
</para>
</change>
<change type="bugfix">
<para>
Fixed style in CHANGES.
2018-12-20 16:17:08 +00:00
module discovery did not work on 64-bit big-endian systems like IBM/S390x.
Added version 1.6 CHANGES.
2018-11-15 12:56:09 +00:00
</para>
</change>
</changes>
Packages: updated to 1.5-1.
2018-10-25 14:49:10 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10
unit-perl
unit-ruby"
ver="1.5" rev="1"
date="2018-10-25" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.5.
</para>
</change>
</changes>
Added version 1.5 CHANGES.
2018-10-25 14:48:56 +00:00
<changes apply="unit" ver="1.5" rev="1"
date="2018-10-25" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="change">
<para>
the "type" of application object for Go was changed to "external".
</para>
</change>
<change type="feature">
<para>
initial version of Node.js package with basic HTTP request-response support.
</para>
</change>
<change type="feature">
<para>
compatibility with LibreSSL.
</para>
</change>
<change type="feature">
<para>
--libdir and --incdir ./configure options to install libunit headers
and static library.
</para>
</change>
<change type="bugfix">
<para>
connection might be closed prematurely while sending response;
the bug had appeared in 1.3.
</para>
</change>
<change type="bugfix">
<para>
application processes might have stopped handling requests, producing
"last message send failed: Resource temporarily unavailable" alerts in log;
the bug had appeared in 1.4.
</para>
</change>
<change type="bugfix">
<para>
Fixed style in CHANGES.
2018-12-20 16:17:08 +00:00
Go applications did not work when Unit was built with musl C library.
Added version 1.5 CHANGES.
2018-10-25 14:48:56 +00:00
</para>
</change>
</changes>
Packages: updated to 1.4-2.
2018-09-27 12:05:03 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10
unit-perl
unit-ruby"
ver="1.4" rev="2"
date="2018-09-27" time="13:30:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="bugfix">
<para>
corrected instructions for launching sample application.
</para>
</change>
</changes>
<changes apply="unit" ver="1.4" rev="2"
date="2018-09-27" time="13:30:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="change">
<para>
the "saveconfig" and "loadconfig" action scripts were removed.
</para>
</change>
</changes>
Added version 1.4 CHANGES.
2018-09-20 15:18:52 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10
unit-perl
unit-ruby"
ver="1.4" rev="1"
date="2018-09-20" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.4.
</para>
</change>
</changes>
<changes apply="unit" ver="1.4" rev="1"
date="2018-09-20" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="change">
<para>
the control API maps the configuration object only at "/config/".
</para>
</change>
<change type="feature">
<para>
TLS support for client connections.
</para>
</change>
<change type="feature">
<para>
TLS certificates storage control API.
</para>
</change>
<change type="feature">
<para>
Unit library (libunit) to streamline language module integration.
</para>
</change>
<change type="feature">
<para>
"408 Request Timeout" responses while closing HTTP keep-alive connections.
</para>
</change>
<change type="feature">
<para>
improvements in OpenBSD support.
Thanks to David Carlier.
</para>
</change>
<change type="bugfix">
<para>
a segmentation fault might have occurred after reconfiguration.
</para>
</change>
<change type="bugfix">
<para>
building on systems with non-default locale might be broken.
</para>
</change>
<change type="bugfix">
<para>
"header_read_timeout" might not work properly.
</para>
</change>
<change type="bugfix">
<para>
header fields values with non-ASCII bytes might be handled incorrectly
in Python 3 module.
</para>
</change>
</changes>
Added version 1.3 CHANGES.
2018-07-13 11:45:08 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10
unit-perl
unit-ruby"
ver="1.3" rev="1"
date="2018-07-13" time="18:00:00 +0300"
packager="Konstantin Pavlov &lt;thresh@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.3.
</para>
</change>
</changes>
<changes apply="unit" ver="1.3" rev="1"
date="2018-07-13" time="18:00:00 +0300"
packager="Konstantin Pavlov &lt;thresh@nginx.com&gt;">
<change type="change">
<para>
UTF-8 characters are now allowed in request header field values.
</para>
</change>
<change type="feature">
<para>
configuration of the request body size limit.
</para>
</change>
<change type="feature">
<para>
configuration of various HTTP connection timeouts.
</para>
</change>
<change type="feature">
<para>
Ruby module now automatically uses Bundler where possible.
</para>
</change>
<change type="feature">
<para>
http.Flusher interface in Go module.
</para>
</change>
<change type="bugfix">
<para>
various issues in HTTP connection errors handling.
</para>
</change>
<change type="bugfix">
<para>
requests with body data might be handled incorrectly in PHP module.
</para>
</change>
<change type="bugfix">
<para>
individual PHP configuration options specified via control API were reset
to previous values after the first request in application process.
</para>
</change>
</changes>
Added version 1.2 CHANGES.
2018-06-07 13:43:37 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6
unit-go unit-go1.7 unit-go1.8 unit-go1.9 unit-go1.10
unit-perl
unit-ruby"
ver="1.2" rev="1"
date="2018-06-07" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.2.
</para>
</change>
</changes>
<changes apply="unit" ver="1.2" rev="1"
date="2018-06-07" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="feature">
<para>
configuration of environment variables for application processes.
</para>
</change>
<change type="feature">
<para>
customization of php.ini path.
</para>
</change>
<change type="feature">
<para>
setting of individual PHP configuration options.
</para>
</change>
<change type="feature">
<para>
configuration of execution arguments for Go applications.
</para>
</change>
<change type="bugfix">
<para>
keep-alive connections might hang after reconfiguration.
</para>
</change>
</changes>
Packages: Ubuntu 18.10 "bionic" support added.
2018-05-14 11:11:37 +00:00
<changes apply="unit-go1.10" ver="1.1" rev="1"
date="2018-05-14" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Go 1.10 module for NGINX Unit.
</para>
</change>
</changes>
Added version 1.1 CHANGES.
2018-04-26 15:30:06 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6
unit-go unit-go1.7 unit-go1.8 unit-go1.9
unit-perl
unit-ruby"
ver="1.1" rev="1"
date="2018-04-26" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.1.
</para>
</change>
</changes>
<changes apply="unit" ver="1.1" rev="1"
date="2018-04-26" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="bugfix">
<para>
Python applications that use the write() callable did not work.
</para>
</change>
<change type="bugfix">
<para>
virtual environments created with Python 3.3 or above might not have worked.
</para>
</change>
<change type="bugfix">
<para>
the request.Read() function in Go applications did not produce EOF
when the whole body was read.
</para>
</change>
<change type="bugfix">
<para>
a segmentation fault might have occurred while access log reopening.
</para>
</change>
<change type="bugfix">
<para>
in parsing of IPv6 control socket addresses.
</para>
</change>
<change type="bugfix">
<para>
loading of application modules was broken on OpenBSD.
</para>
</change>
<change type="bugfix">
<para>
a segmentation fault might have occurred when there were two modules
with the same type and version; the bug had appeared in 1.0.
</para>
</change>
<change type="bugfix">
<para>
alerts "freed pointer points to non-freeble page" might have appeared in log
on 32-bit platforms.
</para>
</change>
</changes>
Added version 1.0 CHANGES.
2018-04-12 16:47:33 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6
unit-go unit-go1.7 unit-go1.8 unit-go1.9
unit-perl
unit-ruby"
ver="1.0" rev="1"
date="2018-04-12" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 1.0.
</para>
</change>
</changes>
<changes apply="unit" ver="1.0" rev="1"
date="2018-04-12" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="change">
<para>
configuration object moved into "/config/" path.
</para>
</change>
<change type="feature">
<para>
basic access logging.
</para>
</change>
<change type="bugfix">
<para>
503 error occurred if Go application did not write response header or body.
</para>
</change>
<change type="bugfix">
<para>
Improved wording in CHANGES.
2018-04-26 13:47:55 +00:00
Ruby applications that use encoding conversions might not have worked.
Added version 1.0 CHANGES.
2018-04-12 16:47:33 +00:00
</para>
</change>
<change type="bugfix">
<para>
various stability issues.
</para>
</change>
</changes>
Added version 0.7 CHANGES.
2018-03-22 18:07:06 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6
unit-go unit-go1.7 unit-go1.8 unit-go1.9
unit-perl"
ver="0.7" rev="1"
date="2018-03-22" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 0.7.
</para>
</change>
</changes>
Added Ruby packaging support.
2018-04-02 12:48:33 +00:00
<changes apply="unit-ruby" ver="0.7" rev="1"
date="2018-04-02" time="15:40:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Ruby module for NGINX Unit.
</para>
</change>
</changes>
Added version 0.7 CHANGES.
2018-03-22 18:07:06 +00:00
<changes apply="unit" ver="0.7" rev="1"
date="2018-03-22" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="feature">
<para>
Ruby application module.
</para>
</change>
<change type="bugfix">
<para>
in discovering modules.
</para>
</change>
<change type="bugfix">
<para>
various race conditions on reconfiguration and during shutting down.
</para>
</change>
<change type="bugfix">
<para>
tabs and trailing spaces were not allowed in header fields values.
</para>
</change>
<change type="bugfix">
<para>
a segmentation fault occurred in Python module if start_response() was called
outside of WSGI callable.
</para>
</change>
<change type="bugfix">
<para>
Improved wording in CHANGES.
2018-04-26 13:47:55 +00:00
a segmentation fault might have occurred in PHP module if there was an error
while initialization.
Added version 0.7 CHANGES.
2018-03-22 18:07:06 +00:00
</para>
</change>
</changes>
Docs: reduced number of similar entries in changes.xml.
2018-02-14 11:40:04 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6
unit-go unit-go1.7 unit-go1.8 unit-go1.9
unit-perl"
ver="0.6" rev="1"
Added version 0.6 CHANGES.
2018-02-09 16:07:55 +00:00
date="2018-02-09" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 0.6.
</para>
</change>
</changes>
<changes apply="unit" ver="0.6" rev="1"
date="2018-02-09" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="bugfix">
<para>
the main process died when the "type" application option contained version;
the bug had appeared in 0.5.
</para>
</change>
</changes>
Docs: reduced number of similar entries in changes.xml.
2018-02-14 11:40:04 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6
unit-go unit-go1.7 unit-go1.8 unit-go1.9"
ver="0.5" rev="1"
Added version 0.5 CHANGES.
2018-02-08 15:42:51 +00:00
date="2018-02-08" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 0.5.
</para>
</change>
</changes>
Packages: added Perl package.
2018-02-07 14:26:37 +00:00
<changes apply="unit-perl" ver="0.5" rev="1"
Added version 0.5 CHANGES.
2018-02-08 15:42:51 +00:00
date="2018-02-08" time="18:00:00 +0300"
Packages: added Perl package.
2018-02-07 14:26:37 +00:00
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Perl module for NGINX Unit.
</para>
</change>
</changes>
Added version 0.5 CHANGES.
2018-02-08 15:42:51 +00:00
<changes apply="unit" ver="0.5" rev="1"
date="2018-02-08" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="change">
<para>
the "workers" application option was removed, the "processes"
application option should be used instead.
</para>
</change>
<change type="feature">
<para>
the "processes" application option with prefork and dynamic
process management support.
</para>
</change>
<change type="feature">
<para>
Perl application module.
</para>
</change>
<change type="bugfix">
<para>
in reading client request body; the bug had appeared in 0.3.
</para>
</change>
<change type="bugfix">
<para>
Improved wording in CHANGES.
2018-04-26 13:47:55 +00:00
some Python applications might not have worked due to missing
Added version 0.5 CHANGES.
2018-02-08 15:42:51 +00:00
"wsgi.errors" environ variable.
</para>
</change>
<change type="bugfix">
<para>
HTTP chunked responses might be encoded incorrectly on 32-bit
platforms.
</para>
</change>
<change type="bugfix">
<para>
infinite looping in HTTP parser.
</para>
</change>
<change type="bugfix">
<para>
segmentation fault in router.
</para>
</change>
</changes>
Docs: reduced number of similar entries in changes.xml.
2018-02-14 11:40:04 +00:00
<changes apply="unit-php
unit-python unit-python2.7
unit-python3.4 unit-python3.5 unit-python3.6
unit-go unit-go1.7 unit-go1.8 unit-go1.9"
ver="0.4" rev="1"
Added version 0.4 CHANGES.
2018-01-15 12:05:25 +00:00
date="2018-01-15" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 0.4.
</para>
</change>
</changes>
<changes apply="unit" ver="0.4" rev="1"
date="2018-01-15" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="feature">
<para>
compatibility with DragonFly BSD.
</para>
</change>
<change type="feature">
<para>
"configure php --lib-static" option.
</para>
</change>
<change type="bugfix">
<para>
HTTP request body was not passed to application;
the bug had appeared in 0.3.
</para>
</change>
<change type="bugfix">
<para>
HTTP large header buffers allocation and deallocation fixed;
the bug had appeared in 0.3.
</para>
</change>
<change type="bugfix">
<para>
Improved wording in CHANGES.
2018-04-26 13:47:55 +00:00
some PHP applications might not have worked with relative "root" path.
Added version 0.4 CHANGES.
2018-01-15 12:05:25 +00:00
</para>
</change>
</changes>
Packages: added support for Ubuntu 17.10.
2017-12-28 17:38:35 +00:00
<changes apply="unit-go1.9" ver="0.3" rev="1"
date="2017-12-28" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Go 1.9 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-python3.6" ver="0.3" rev="1"
date="2017-12-28" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Python 3.6 module for NGINX Unit.
</para>
</change>
</changes>
Docs: reduced number of similar entries in changes.xml.
2018-02-14 11:40:04 +00:00
<changes apply="unit-php
unit-python unit-python2.7 unit-python3.4 unit-python3.5
unit-go unit-go1.7 unit-go1.8"
ver="0.3" rev="1"
Added version 0.3 CHANGES.
2017-12-28 13:01:06 +00:00
date="2017-12-28" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
NGINX Unit updated to 0.3.
</para>
</change>
</changes>
<changes apply="unit" ver="0.3" rev="1"
date="2017-12-28" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="change">
<para>
the Go package name changed to "nginx/unit".
</para>
</change>
<change type="change">
<para>
in the "limits.timeout" application option: application start time and
time in queue now are not accounted.
</para>
</change>
<change type="feature">
<para>
the "limits.requests" application option.
</para>
</change>
<change type="feature">
<para>
application request processing latency optimization.
</para>
</change>
<change type="feature">
<para>
HTTP keep-alive connections support.
</para>
</change>
<change type="feature">
<para>
the "home" Python virtual environment configuration option.
</para>
</change>
<change type="feature">
<para>
Python atexit hook support.
</para>
</change>
<change type="feature">
<para>
various Go package improvements.
</para>
</change>
<change type="bugfix">
<para>
various crashes fixed.
</para>
</change>
</changes>
Introduced rpm packages building tools.
2017-10-19 15:23:31 +00:00
<changes apply="unit-go" ver="0.2" rev="1"
date="2017-10-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Go module for NGINX Unit.
</para>
</change>
</changes>
Introduced deb packages building tools.
2017-10-19 15:23:32 +00:00
<changes apply="unit-go1.7" ver="0.2" rev="1"
date="2017-10-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Go 1.7 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-go1.8" ver="0.2" rev="1"
date="2017-10-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Go 1.8 module for NGINX Unit.
</para>
</change>
</changes>
Introduced rpm packages building tools.
2017-10-19 15:23:31 +00:00
<changes apply="unit-python" ver="0.2" rev="1"
date="2017-10-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Python module for NGINX Unit.
</para>
</change>
</changes>
Introduced deb packages building tools.
2017-10-19 15:23:32 +00:00
<changes apply="unit-python2.7" ver="0.2" rev="1"
date="2017-10-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Python 2.7 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-python3.4" ver="0.2" rev="1"
date="2017-10-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Python 3.4 module for NGINX Unit.
</para>
</change>
</changes>
<changes apply="unit-python3.5" ver="0.2" rev="1"
date="2017-10-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of Python 3.5 module for NGINX Unit.
</para>
</change>
</changes>
Introduced rpm packages building tools.
2017-10-19 15:23:31 +00:00
<changes apply="unit-php" ver="0.2" rev="1"
date="2017-10-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
Initial release of PHP module for NGINX Unit.
</para>
</change>
</changes>
Added version 0.2 CHANGES.
2017-10-19 14:54:29 +00:00
<changes apply="unit" ver="0.2" rev="1"
date="2017-10-19" time="18:00:00 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change type="feature">
<para>
configuration persistence.
</para>
</change>
<change type="feature">
<para>
improved handling of configuration errors.
</para>
</change>
<change type="feature">
<para>
application "timeout" property.
</para>
</change>
<change type="bugfix">
<para>
POST request for PHP were handled incorrectly.
</para>
</change>
<change type="bugfix">
<para>
the router exited abnormally if all listeners had been deleted.
</para>
</change>
<change type="bugfix">
<para>
the router crashed under load.
</para>
</change>
<change type="bugfix">
<para>
memory leak in the router.
</para>
</change>
</changes>
Added changelogs generation tools.
2017-10-19 14:48:58 +00:00
<changes apply="unit" ver="0.1" rev="1"
date="2017-09-06" time="19:14:28 +0300"
packager="Andrei Belov &lt;defan@nginx.com&gt;">
<change>
<para>
First public release.
</para>
</change>
</changes>
</change_log>
Reference in a new issue Copy permalink