> what about setting up a proxy/loadbalancer like nginx/haproxy and let him do
> the ssl termination?
> and hide the backend completly, that is, let frontend communicate only with
> the proxy/lb?
> why not connect via ssl always?
The websocket server is part of an application each user downloads
Am Tue, 28 Jul 2020 08:05:46 +0200
schrieb Alexander Carôt :
> Hallo Marten,
>
> thanks for your additionl reply !
>
> There are two reasons why I have to use a secure websocket:
>
> 1.) In some cases our website connects to our app not on localhost but some
> other place on the LAN.
>
> 2.)
Hallo Marten,
thanks for your additionl reply !
There are two reasons why I have to use a secure websocket:
1.) In some cases our website connects to our app not on localhost but some
other place on the LAN.
2.) Our site is part of a CMS-based project which per default runs with SSL.
Changing
Hello Alexander,
I don't know (or recall) what your setup is like. The following answer assumes
the website you refer to also runs on the local machine:
Somewhat going in the other direction I'd say wss/https is not necessary if
your application actually only listens to localhost (127.0.0.1/[::
