# Twitter oneboxed content breaking ssl

**URL:** <https://meta.discourse.org/t/twitter-oneboxed-content-breaking-ssl/29670>\
**Category:** Bug\
**Created:** [5. Juni 2015 um 03:37 UTC](https://meta.discourse.org/t/twitter-oneboxed-content-breaking-ssl/29670 "2015-06-05T03:37:23Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![watchmanmonitor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/watchmanmonitor/32/430970_2.png) [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)\
**Post date:** [5. Juni 2015 um 03:37 UTC](https://meta.discourse.org/t/twitter-oneboxed-content-breaking-ssl/29670/1 "2015-06-05T03:37:23Z")

</div>

I just posted a twitter link on my hosted discourse, and the page no longer had a nice ssl lock.

I see this:

```plaintext
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 insecure image 'http://pbs.twimg.com/profile_images/518242033811472386/VKcAQvEB_normal.png'. This content should also be served over HTTPS.
discourse/lib/Markdown.Editor:995 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.
ember.prod:3051 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.

```

and I know that all the calls to `http://pbs.twimg.com` could be `https://pbs.twimg.com`

Is this a fix that the discourse team can pull off? or is it up to the official twitter setup?

---

_[View the full topic](https://meta.discourse.org/t/twitter-oneboxed-content-breaking-ssl/29670)._