When someone posts a http link in their post and it gets oneboxed, this triggers a TLS mixed content warning (and the browser no longer displays the page as secure) This issue has been discussed in a number of topics (see end of post) and I gather from these discussions (especially https://meta.dis…

I’m confused on the workaround here. If the original content is HTTPS should there still need to be an “indent” before including? If so, what kind of “indent” is it?

[Bild] RyanK: I’m confused on the workaround here. If the original content is HTTPS should there still need to be an “indent” before including? If so, what kind of “indent” is it? If the original content is HTTPS there is nothing to do, a link will get oneboxed just fine. For HTTP we have…

Oneboxed http link causes a TLS mixed content warning

Product Support

codinghorror (Jeff Atwood) 9. April 2017 um 18:43 2

You would need to mirror the entire http content somewhere as https, which is wildly out of scope for our project.

Thema		Antworten	Aufrufe
Links to Amazon cause a TLS mixed content warning Bug	5	1817	11. Januar 2016
MediaFire onebox uses insecure image Product Support onebox	3	1070	25. Januar 2018
Twitter oneboxed content breaking ssl Bug	3	2237	9. Juni 2015
Whitelist to allow onebox only with https domains? Product Support	6	1175	29. Oktober 2018
Mixed content due to hotlinked images Product Support	12	1831	14. Dezember 2019

Oneboxed http link causes a TLS mixed content warning

Verwandte Themen