# Oneboxed http link causes a TLS mixed content warning

**URL:** <https://meta.discourse.org/t/oneboxed-http-link-causes-a-tls-mixed-content-warning/60688>\
**Category:** Product Support\
**Created:** [9 أبريل 2017، 4:37م UTC](https://meta.discourse.org/t/oneboxed-http-link-causes-a-tls-mixed-content-warning/60688 "2017-04-09T16:37:32Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [9 مايو 2017، 7:10م UTC](https://meta.discourse.org/t/oneboxed-http-link-causes-a-tls-mixed-content-warning/60688/4 "2017-05-09T19:10:43Z")

</div>

> [@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.

---

_[View the full topic](https://meta.discourse.org/t/oneboxed-http-link-causes-a-tls-mixed-content-warning/60688)._