Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Secured connection #5

Open
krajcikondra opened this issue Jul 2, 2019 · 0 comments
Open

Secured connection #5

krajcikondra opened this issue Jul 2, 2019 · 0 comments

Comments

@krajcikondra
Copy link

Secured connections is not easy for configuration. There are some problems with handshake in react.

Easier way is:

  1. In apache load modules: proxy_http, proxy, proxy_wstunnel
    You can use command: a2enmod proxy_http proxy proxy_wstunnel

  2. 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.

  1. 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.

  1. In javascript connect to websocket server
    IPub.WebSockets.WAMP.initialize('wss://myweb.com/websockets');

This configuration works for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant