# 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:** 6

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [25 november 2020 om 17:29 UTC](https://meta.discourse.org/t/changing-force-https-does-not-update-the-url-of-uploaded-images-causing-a-mixed-content-warning/171290/6 "2020-11-25T17:29:57Z")

</div>

This is an issue even if the proxy is sending the `X-Forwarded-Proto` header and all.

Toggling the `force_https` site setting will not update the logo URL protocol until the `icon_manager` cache has been cleared. Adding force\_https to the [watched settings](https://github.com/discourse/discourse/blob/master/lib/site_icon_manager.rb#L20) for the icon manager is probably the easiest solution.

---

_[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)._
