Versions Compared

Old Version 5

changes.mady.by.user John Sinclair

Saved on

compared with

New Version 6

changes.mady.by.user John Sinclair

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

There are two parts to making this work - having the client connect on wss: port 443 and having the proxy forward the events URL to the websocket for OMK.

Request the clients browser to use 443 for the websocket

To tell the clients browser to use 443 (and hence wss: with SSL/TLS) instead of the default port 8042 (ws:) change the following in opCommon.nmis.  

Code Block
languageperl
titleopCommon.nmis set websocket port
  'websocket_proxy_port' => '443'


Proxy the connection from your SSL/TLS termination to the OMK webservice

The client's websocket will now be coming through the same SSL/TLS Transport as your HTTPS traffic on port 443.  We need the proxy server to forward the websocket to the OMK webservice much like the HTTP traffic. 

...

Info
titleAdditional Apache Configuration items and their impact
Proxy WS Tunnel module 
The Apache WS proxy tunnel Module needs to be enabled for ProxyPass to work for ws.
On most systems this can be found as "proxy_wstunnel.load" you will probably find this file in mods-available and simply need to link it mods-enabled.  Your Apache setup might use other configuration methods to load modules so please do check.

WSS HTTPS interaction

Please note apache will force the use of WSS (SSL websocket) if you are using HTTPS.  This is because the apache configuration:

RequestHeader set X-Forwarded-Proto “https"https"
As the X-Forwarded-Proto HTTP header is seen by the OMK webservice, it therefortherefore sets the connection URLs to be wss not ws.

...