# 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:** [December 24, 2014, 2:06pm 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:** 10

<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:** [December 25, 2014, 4:17am UTC](https://meta.discourse.org/t/try-to-force-https-instead-of-downloading-remote-images/23399/10 "2014-12-25T04:17:13Z")

</div>

> [@codinghorror](#):
>
> Download remote images exists so that images can’t be pulled or remote sites go offline, breaking your post when the image disappears.

Exactly. As I expressed above in another reply to the OP: the integrity of my forum’s archive means everything to me. A few extra milliseconds (or even a full second or two) for someone in Australia to download images from my New Jersey location is, I think, a good trade off for a very long-term and important commitment.

---

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