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

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.

show more ...

Java: upgrading third-party components.

Tests: client IP address replacement.

Tests: initialising log params before first _print_log().

Tests: retrying directory remove if resource is busy.

Java: upgrading third-party components.

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

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
}
}
]
}

show more ...

Router: fixed segmentation fault.

In the case that routes or upstreams is empty and the pass option is a variable.
If the resolved pass is routes or upstreams, a segment error occurred.

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 en

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.

show more ...

Tests: added SNI test without hostname in request.

Tests: use mutex with multitthreaded Ruby hooks.

This commit fixes a rare crash that can occur when File.write is
called by many threads.

Tests: print_log_on_assert() decorator introduced.

Tests: address configuration tests reworked.

Tests: Ruby hooks.

Tests: run Ruby applications inside temporary directory.

Tests: fixing racing condition in respawn tests.

A race may occur between the router process restart and the main process
sending a notification to the running controller. For example, a test scrip

Tests: fixing racing condition in respawn tests.

A race may occur between the router process restart and the main process
sending a notification to the running controller. For example, a test script
detects the new process and starts performing a smoke test, but the controller
has not yet received the 'remove PID' notification, so the connection to the
router is broken and any attempt to update the configuration will cause an
error.

The solution is to perform several attempts to reconfigure Unit with a short
delay between failures.

show more ...

Fixing multiple TLS-enabled listeners initialization.

Because of the incorrect 'last' field assignment, multiple listeners with
a TLS certificate did not initialize properly, which caused a router c

Fixing multiple TLS-enabled listeners initialization.

Because of the incorrect 'last' field assignment, multiple listeners with
a TLS certificate did not initialize properly, which caused a router crash
while establishing a connection.

Test with multiple TLS listeners added.

The issue was introduced in the c548e46fe516 commit.

This closes #561 issue on GitHub.

show more ...

Tests: renamed share to static.

Also minor style changes.

Tests: chroot test with permissions skipped under root.

Tests: added tests for TLS "conf_commands" option.

Tests: added TLS test without close notify.

Static: handled unknown MIME types when MIME-filtering active.

Go: fixing tests for Go 1.16.

In Go 1.16, the module-aware mode is enabled by default; to fall back to
previous behavior, the GO111MODULE environment variable should be set to
'auto'.

Details: http

Go: fixing tests for Go 1.16.

In Go 1.16, the module-aware mode is enabled by default; to fall back to
previous behavior, the GO111MODULE environment variable should be set to
'auto'.

Details: https://golang.org/doc/go1.16

show more ...

Tests: added additional check in tests with timeouts.

Tests: test_settings_send_timeout improved.

Data length adjusts depending on socket buffer size when it's possible.