You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a page served over HTTPS tries to access a non secure websocket connection (i.e. ws:// instead of wss://) the browser throws a SecurityError.
You can disable this behavior in firefox with the flag network.websocket.allowInsecureFromHTTPS, but it the only way to solve it reliably is to serve the page over HTTP.
In cc5c354 I added some code to check for the error whenever a websocket is initiated and automatically change the protocol to HTTP, but that only happens when you choose a ClockIOT.
For now, I'm going to add some code to wyolum.com's .htaccess file so that it automatically redirects HTTPS to HTTP on the UI page. http://wyolum.com/clockiot/UI
The text was updated successfully, but these errors were encountered:
When a page served over HTTPS tries to access a non secure websocket connection (i.e. ws:// instead of wss://) the browser throws a SecurityError.
You can disable this behavior in firefox with the flag
network.websocket.allowInsecureFromHTTPS
, but it the only way to solve it reliably is to serve the page over HTTP.In cc5c354 I added some code to check for the error whenever a websocket is initiated and automatically change the protocol to HTTP, but that only happens when you choose a ClockIOT.
For now, I'm going to add some code to wyolum.com's .htaccess file so that it automatically redirects HTTPS to HTTP on the UI page. http://wyolum.com/clockiot/UI
The text was updated successfully, but these errors were encountered: