Bug#880195: apache2: Trying to use ws:// in proxy results in "No protocol handler was valid for the URL /ws .... "

[Martin Sebald <msebald@hot-chilli.net>]

Hello all,

I am experiencing the same problem as described here with apache2 version
2.4.38-3+deb10u3 (buster) and also version 2.4.43-1~bpo10+1 (buster-backports).

The proxy modules are loaded but I cannot proxy WebSocket with Apache2. Here's
some more information:


"apache2ctl -M | grep proxy" gives me:

proxy_module (shared)
proxy_http_module (shared)
proxy_wstunnel_module (shared)

I'm trying to proxy WebSocket of Prosody XMPP Server like described here:
https://prosody.im/doc/websocket

This is in my vHost config:

<IfModule mod_proxy.c>
    <IfModule mod_proxy_wstunnel.c>
    ProxyTimeout 900
    <Location "/xmpp-websocket">
        ProxyPreserveHost On
        ProxyPass "ws://localhost:5280/xmpp-websocket"
    </Location>
    </IfModule>
</IfModule>

It does not matter if I try to proxy "ws" or "wss".

The error message is the following:

[Wed Jul 22 23:19:46.651199 2020] [proxy:warn] [pid 13332:tid 139973210351360]
[client xxx] AH01144: No protocol handler was valid for the URL
/xmpp-websocket (scheme 'wss'). If you are using a DSO version of mod_proxy,
make sure the proxy submodules are included in the configuration using LoadModule.

[Wed Jul 22 23:37:54.853492 2020] [proxy:warn] [pid 8816:tid 140146156889856]
[client xxx] AH01144: No protocol handler was valid for the URL
/xmpp-websocket (scheme 'wss'). If you are using a DSO version of mod_proxy,
make sure the proxy submodules are included in the configuration using LoadModule.


Is this a bug or some configuration thing? I doublechecked everything and I
think it is a bug.

Looking forward for help.

Thank you and regards,
Martin