Ah, ok thanks. I’m running the web server unencrypted as well, for the same reason.
-Les > On Jul 25, 2021, at 4:14 AM, Karen K <[email protected]> wrote: > > ln77 schrieb am Sonntag, 25. Juli 2021 um 03:35:38 UTC+2: >> I don’t see the point of SSL on the websockets connection from the browser. >> The data is all public, there’s nothing sensitive sent by the client, and if >> someone spoofs the mqtt broker, who really cares? > > The web browser cares. If it receives the website by HTTPS (SSL encrypted), > then it refuses to connect to an unencrypted websockets server. > >> > > -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/08aa26d4-d986-4916-9c82-4c895c8b8fddn%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/4C1AF58F-A4E6-413C-9724-01F248E382B0%402pi.org.
