Our education community allows users to use iframes to insert H5P (HTML5) content which works great as an allowed iframe URL. But one content type that embeds an audio recorder is reporting this error: [not-https] All of our discourse content is served as HTTPs, and all urls in the embed are HTT…

Have you upgraded from the command line recently? Is force_https enabled?

There’s been a command line upgrade in the last 3 weeks. I am finding references to enabling force_https but not how to do this. As not a full on sys admin type but someone with all the keys, can you 'splain it to me?

If you search the admin settings for “force” and don’t see force_https, then it’s set already. FWIW, I don’t see any http errors on the page you link.

Okay thanks, it’s not there. The developers of the software indicate its probably not an HTTPS issue after all (they acknowledge a poorly worded error message) and more likely an issue of the iframe not granting the feature policy to request access to the microphone (adding allow=“microphone *” did…

The issue is to grant access to the microphone via an iframe allow= parameter is stripped from iframe tags in discourse, as reported elsewhere .

Un iframe dans un post ne rapporte pas HTTPs

Soutien

cogdog (Alan Levine) Novembre 4, 2021, 6:59 6

Le problème est que l’accès au microphone via le paramètre allow dans une balise <iframe> est supprimé dans Discourse, comme signalé ailleurs.

Sujet		Réponses	Vues
Replacement for whitelist-iframe Support	3	1890	Avril 27, 2020
How to run the discourse in Iframe? Support	1	387	Avril 17, 2023
Restrict embedded video to HTTPS Support	1	459	Janvier 3, 2021
Add WhiteListIframe embed of everycircuit.com Support	11	2402	Septembre 16, 2019
Discourse not shown in iframe Support unsupported-install	30	8551	Avril 26, 2021

Un iframe dans un post ne rapporte pas HTTPs

Sujets connexes