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.discourse.org/t/download-images-for-oneboxes-as-well-if-download-images-is-set/21103/) that this is a complex issue to resolve. I understand that a workaround is indent those insecure urls to make sure they don’t get oneboxed. (But this is not something to explain to the average user, especially if we want to simultaneously teach them to use oneboxes.) What I don’t understand is what the current state of affairs is regarding this. Is this on the roadmap? Is it ultimately not fixable? Is there something the individual site-admin can do? I believe that this topic reflects the latest state of the discussion but is seems inconclusive too: https://meta.discourse.org/t/download-images-for-oneboxes-as-well-if-download-images-is-set/21103/ So, beyond the technical debate: what can/should site-admins do about this? Previous discussions of this issue: [image] Twitter oneboxed content breaking ssl Bug I just posted a twitter link on my hosted discourse, and the page no longer had a nice ssl lock. I see this: Mixed Content: The page at 'https://forum.somedomain.com/t/pricing/43/3' was loaded over HTTPS, but requested an insecure image 'http://pbs.twimg.com/profile_images/518242033811472386/VKcAQvEB_normal.png'. This content should also be served over HTTPS. 2ember.prod:3051 Mixed Content: The page at 'https://forum.somedomain.com/t/pricing/43/3' was loaded over HTTPS, but requested an insecu… https://meta.discourse.org/t/dont-load-http-onebox-images-when-using-https/27530 [image] Links to Amazon cause a TLS mixed content warning Bug Linking to Amazon in a topic causes a mixed content warning when using https, presumably because the thumbnail is loaded from a third party over http. Would it be possible to load the thumbnail using https instead?

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?

[image] 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 a open PR pending a test that will get merged soonish.

Oneboxed http link causes a TLS mixed content warning

Product Support

codinghorror (Jeff Atwood) April 9, 2017, 6:43pm 2

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

Topic		Replies	Views
Links to Amazon cause a TLS mixed content warning Bug	5	1829	January 11, 2016
MediaFire onebox uses insecure image Product Support onebox	3	1091	January 25, 2018
Twitter oneboxed content breaking ssl Bug	3	2268	June 9, 2015
Whitelist to allow onebox only with https domains? Product Support	6	1201	October 29, 2018
Mixed content due to hotlinked images Product Support	12	1861	December 14, 2019

Oneboxed http link causes a TLS mixed content warning

Related topics