search

hologfx / holographics-issues

This repository is for tracking bugs and issues with Holographics that our users may want to contribute.
MIT License
1 stars 0 forks source link

Request Socket.io connection through https instead of http #23

Open Toshiba01 opened 3 years ago

Toshiba01 commented 3 years ago

Hi! Nowadays, we're making everything remote. We have set-up a remote user to use Hologfx via a reverse-proxy, all good, but we're getting errors because we have content served from mixed sources (http/https).

control.js:179 Mixed Content: The page at 'https://our.domain/control/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://our.domain/socket.io/?EIO=3&transport=polling&t=NR-B0Tz'. This request has been blocked; the content must be served over HTTPS.

Is there a way where we can serve it through https? Thanks!

paolohu commented 3 years ago

same - it should use the same protocol/port that was originally requested

paolohu commented 3 years ago

in my case (loading hologfx in an iframe) adding this meta tag to the main site made it work:

`

`