Secured connections is not easy for configuration. There are some problems with handshake in react.
Easier way is:
-
In apache load modules: proxy_http, proxy, proxy_wstunnel
You can use command: a2enmod proxy_http proxy proxy_wstunnel
-
To your httpd-vhost.conf add at the begin
ProxyPass /websocket ws://127.0.0.1:8888
ProxyPassReverse /websocket ws://127.0.0.1:8888
Traffic will be secured between client and proxy. After proxy will be communication unsecured.
- My neon configuration
webSockets: clients: storage: driver: @clients.driver.memory ttl: 0 server: httpHost: localhost port: 8888 address: 0.0.0.0 routes: '/test/<handle>' : 'Test"' mapping: *: App\WebsocketControllers\*Controller
I have not specified secured because between application and proxy is communication unsecured.
- In javascript connect to websocket server
IPub.WebSockets.WAMP.initialize('wss://myweb.com/websockets');
This configuration works for me.
Secured connections is not easy for configuration. There are some problems with handshake in react.
Easier way is:
In apache load modules: proxy_http, proxy, proxy_wstunnel
You can use command:
a2enmod proxy_http proxy proxy_wstunnelTo your httpd-vhost.conf add at the begin
Traffic will be secured between client and proxy. After proxy will be communication unsecured.
webSockets: clients: storage: driver: @clients.driver.memory ttl: 0 server: httpHost: localhost port: 8888 address: 0.0.0.0 routes: '/test/<handle>' : 'Test"' mapping: *: App\WebsocketControllers\*ControllerI have not specified secured because between application and proxy is communication unsecured.
IPub.WebSockets.WAMP.initialize('wss://myweb.com/websockets');This configuration works for me.