Am Tue, 28 Jul 2020 08:05:46 +0200 schrieb Alexander Carôt <alexander_ca...@gmx.net>:
> 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 the specific sites to no-SSL (http) and the corresponding ws leades
> to mixed content often ignored by the browser.
>
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?
--
/*
* raw_printk("Oops: bitten by watchdog\n");
* linux-2.6.19/arch/cris/arch-v32/kernel/time.c
*/
pgpPmpBrVpyn_.pgp
Description: Digitale Signatur von OpenPGP
_______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
