# בעיה של 'Blocked loading mixed active content' הקשורה לפונטים

**URL:** <https://meta.discourse.org/t/blocked-loading-mixed-active-content-issue-related-to-fonts/195711>\
**Category:** Product Support\
**Created:** [1 ביולי,‏ 2021,‏ 11:23pm UTC](https://meta.discourse.org/t/blocked-loading-mixed-active-content-issue-related-to-fonts/195711 "2021-07-01T23:23:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/griffin/32/223139_2.png) [@griffin](https://meta.discourse.org/u/griffin)\
**Post date:** [2 ביולי,‏ 2021,‏ 12:30am UTC](https://meta.discourse.org/t/blocked-loading-mixed-active-content-issue-related-to-fonts/195711/2 "2021-07-02T00:30:01Z")

</div>

Do the URLs of the mentioned resources _inside_ the page actually begin with “https”? Any resource loaded with an “http” URL will be considered mixed content.

One hack/bandaid you can use is to include the following header in the offending page:

`<meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">`

That will “encourage” the mixed resources to be loaded over “https” while you find the root causes.

---

_[View the full topic](https://meta.discourse.org/t/blocked-loading-mixed-active-content-issue-related-to-fonts/195711)._
