# force\_https wijzigen werkt de url van geüploade afbeeldingen niet bij, wat een mixed content waarschuwing veroorzaakt

**URL:** <https://meta.discourse.org/t/changing-force-https-does-not-update-the-url-of-uploaded-images-causing-a-mixed-content-warning/171290>\
**Category:** Bug\
**Created:** [25 november 2020 om 14:21 UTC](https://meta.discourse.org/t/changing-force-https-does-not-update-the-url-of-uploaded-images-causing-a-mixed-content-warning/171290 "2020-11-25T14:21:50Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![JanKanis](https://avatars.discourse-cdn.com/v4/letter/j/a183cd/32.png) [@JanKanis](https://meta.discourse.org/u/JanKanis)\
**Post date:** [25 november 2020 om 14:21 UTC](https://meta.discourse.org/t/changing-force-https-does-not-update-the-url-of-uploaded-images-causing-a-mixed-content-warning/171290/1 "2020-11-25T14:21:50Z")

</div>

I just enabled `force_https` on my Discourse installation. The https termination is handled by a reverse proxy in front of it. Enabling `force_https` switches most of Discourse’s internal links to https, but not those for already existing images and specifically favicons and logo. Now accessing my site over https causes a mixed content warning due to the non-https images being included.

The links can be made to be https by re-uploading the images or by executing `SiteIconManager.ensure_optimized!` from the rails console, so apparently the link is being cached somewhere and not updated when `force_https` is changed.

Discourse should update the links to its uploaded images (and probably all uploads) when `force_https` is toggled. Or even better would be to not include the scheme in those links, though I don’t know if that is possible.

---

_[View the full topic](https://meta.discourse.org/t/changing-force-https-does-not-update-the-url-of-uploaded-images-causing-a-mixed-content-warning/171290)._
