Since Apache HTTP Server 2.4.47, protocol Upgrade (tunneling) can be better handled by
See Protocol Upgrade.
This module requires the service of
Proxying requests to a websockets server like echo.websocket.org
can be done using the
Proxying both HTTP and websockets at the same time can be done by specifying the websockets
Load balancing for multiple backends can be achieved using
The module can also be used to upgrade to other protocols than WebSocket, by setting
the upgrade parameter in the
upgrade=NONE
and upgrade=ANY
values may be used for
testing/forcing the upgrade but they are not recommended in production for
security reasons.
NONE
means that the check for the header is omitted but still the upgrade/tunneling to
WebSocket always happens.
ANY
means that the upgrade/tunneling will happen using any protocol asked by the client.
Since httpd 2.4.47,
Setting to Off lets
This directive instructs the server to try to create an asynchronous tunnel. If the current MPM does not support the necessary features, a synchronous tunnel is used.
Async support is experimental and subject to change.
This directive imposes a maximum amount of time for the tunnel to be left open while idle. The timeout is considered in seconds by default, but it is possible to increase the time resolution to milliseconds adding the ms suffix.
If
Async support is experimental and subject to change.