diff options
| author | Max Romanov <max.romanov@nginx.com> | 2021-09-20 09:01:08 +0300 |
|---|---|---|
| committer | Max Romanov <max.romanov@nginx.com> | 2021-09-20 09:01:08 +0300 |
| commit | c07f3d3ff693025fc90a72e9c9947bfd457da11e (patch) | |
| tree | fb055563860e40a5b2d94bad57932f6e86e0d8a0 /docs/changes.xml | |
| parent | d21ebcce833ff10dd1e199a75d523f81b5549b6d (diff) | |
| download | unit-c07f3d3ff693025fc90a72e9c9947bfd457da11e.tar.gz unit-c07f3d3ff693025fc90a72e9c9947bfd457da11e.tar.bz2 | |
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.
Diffstat (limited to '')
| -rw-r--r-- | docs/changes.xml | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/changes.xml b/docs/changes.xml index 4519f6e9..5855466e 100644 --- a/docs/changes.xml +++ b/docs/changes.xml @@ -37,6 +37,13 @@ fixed building with glibc 2.34, notably Fedora 35. </para> </change> +<change type="bugfix"> +<para> +established WebSocket connections could stop reading frames from the client +after the corresponding listener had been reconfigured. +</para> +</change> + </changes> |