Libor Klepáč
2017-10-30 14:10:03 UTC
Package: apache2
Version: 2.4.25-3+deb9u3
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Maintainer,
i'm trying to enable websocket proxy for customer on web server running Stretch.
After enabling module
# a2enmod proxy_wstunnel
Considering dependency proxy for proxy_wstunnel:
Module proxy already enabled
Enabling module proxy_wstunnel.
To activate the new configuration, you need to run:
systemctl restart apache2
and restarting apache, i try to use this snippet in vhost configuration
<IfModule mod_proxy_wstunnel.c>
ProxyPass "/ws" "ws://127.0.0.1:9000/"
ProxyPassReverse "/ws" "ws://127.0.0.1:9000/"
ProxyPass "/wss" "ws://127.0.0.1:9000/"
ProxyPassReverse "/wss" "ws://127.0.0.1:9000/"
</IfModule>
it ends with internal server error and log says
AH01144: No protocol handler was valid for the URL /ws. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
Acording to
# apache2ctl -M | grep proxy
proxy_module (shared)
proxy_http_module (shared)
proxy_wstunnel_module (shared)
all modules are loaded.
This apache runs MPM prefork+itk, I also tried on another host, running same version but with MPM event, to eliminate influence of itk (I know, it cannot be run with mod_http2 for example), with same result.
Don't know, what to test next
With regards,
Libor
Version: 2.4.25-3+deb9u3
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Maintainer,
i'm trying to enable websocket proxy for customer on web server running Stretch.
After enabling module
# a2enmod proxy_wstunnel
Considering dependency proxy for proxy_wstunnel:
Module proxy already enabled
Enabling module proxy_wstunnel.
To activate the new configuration, you need to run:
systemctl restart apache2
and restarting apache, i try to use this snippet in vhost configuration
<IfModule mod_proxy_wstunnel.c>
ProxyPass "/ws" "ws://127.0.0.1:9000/"
ProxyPassReverse "/ws" "ws://127.0.0.1:9000/"
ProxyPass "/wss" "ws://127.0.0.1:9000/"
ProxyPassReverse "/wss" "ws://127.0.0.1:9000/"
</IfModule>
it ends with internal server error and log says
AH01144: No protocol handler was valid for the URL /ws. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
Acording to
# apache2ctl -M | grep proxy
proxy_module (shared)
proxy_http_module (shared)
proxy_wstunnel_module (shared)
all modules are loaded.
This apache runs MPM prefork+itk, I also tried on another host, running same version but with MPM event, to eliminate influence of itk (I know, it cannot be run with mod_http2 for example), with same result.
Don't know, what to test next
With regards,
Libor