Description
We use iframe to embed zoom web client on our web page. Today all the meeting request https://zoom.us/j/meeting_id are re-directed to http://zoom.us/j/meeting_id, and therefore blocked by the browser. When try to join the meeting, it only shows a blank page.
Smartphone (please complete the following information):
Browser: Tested on chrome and safari
Additional context
It suddenly happened today, previously it works fine.
FWIW I also reported this here: Web client has stopped working when embedded in an IFRAME and Iâve seen several other reports. Though none with a reply. We ended up scrambling to use the WebSDK instead as that was the only fix we could find.
Try to use another join url like this <iframe src=âhttps://zoom.us/wc/join/11111111111â sandbox=âallow-same-origin allow-forms allow-scriptsâ allowfullscreen=âallowfullscreenâ></iframe>
Yeah, we did make sure. A lot of people have the same error though. Seems like the issue is on your end guys, since the error says that https:// version of your page cannot display insecure content from âthe same page but http:// ?â
Sounds more like an internal issue to me. Could you please investigate this further?
Is there any update on this? With your latest change we are also hitting the same issue here.
As we canât use your websdk due to itâs huge dependencies (we are rolling on a PWA here) we need iframe to work.
Blockquote
Mixed Content: The page at ââŚâ was loaded over HTTPS, but requested an insecure frame ââŚzoomlinkâ This request has been blocked; the content must be served over HTTPS.
Blockquote
Hey @tommy, weâre also running into this issue. This is huge blocker for us as weâre just about to roll out our application. Please let us know if you have any ways around this issue. Thanks a bunch for your help!
I have ran into this problem too and checked the headers sent from the zoom server.
Even though the initial request is âhttps://zoom.us/wc/âŚâ the server redirects with a â302 foundâ to a http-url.
When the browser requests this http-url, the zoom server redirects again to https.
For a normal user in a browser window, this is not a problem.
Inside an iframe you get the Mixed Content Error.
The error could be fixed by zoom by changing the first redirect to https.
I haved fixed this problem on our side with a server2server check on the url, following the redirects to the final url.
After that I pass this final url into the users iframe and it works.
Hi Tommy⌠i keep seeing you suggest to avoid using and iframe and start using the SDK, but SDK was my fist implementation and had terrible bad quality making it impossible to use⌠so in another topic i saw they suggested using an iframe instead
AFAIK
iframe over https does not work, and if you serve via http you receive a message telling you âaudio is not compatible please update your browserâ
1.7.9 WEB SDK let you connect but you cannot use it actually due the very bad quality , annoying sound
is there a working way to implement zoom via web? any suggestions? or requirements to make is work?