# Try to force https instead of downloading remote images

**URL:** <https://meta.discourse.org/t/try-to-force-https-instead-of-downloading-remote-images/23399>\
**Category:** Feature\
**Created:** [24.Декабрь.2014 14:06:27 UTC](https://meta.discourse.org/t/try-to-force-https-instead-of-downloading-remote-images/23399 "2014-12-24T14:06:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![purldator](https://avatars.discourse-cdn.com/v4/letter/p/bcef8e/32.png) [@purldator](https://meta.discourse.org/u/purldator)\
**Post date:** [24.Декабрь.2014 14:16:27 UTC](https://meta.discourse.org/t/try-to-force-https-instead-of-downloading-remote-images/23399/2 "2014-12-24T14:16:27Z")

</div>

> [@Moter8](#):
>
> the users get the images faster (Imgur will have a better CDN than your small site).

When you mean ‘your small site’, do you mean every Discourse user who self-hosts? Or just the hosted Discourse instances offered by the devs?

As a different viewpoint: I prefer to have all remote images downloaded to me if the poster of the image _wants_ that. If they don’t want their image on my server, I am okay with that too, and I’ll honor that. If imgur has a hiccup or ever goes down, then my inline images become broken. Pushing a hosting responsibility away from me and onto a third party leaves the chance that I have no control over what happens to the images served from that third party.

But I do agree there should be an option if an admin wishes to serve images from imgur or any other third party. And I also agree if a well-known site serves https, then it should reflect with links in the conversation to make sure the connection is always secure.

---

_[View the full topic](https://meta.discourse.org/t/try-to-force-https-instead-of-downloading-remote-images/23399)._