# Mixed Content warnings

**URL:** <https://meta.discourse.org/t/mixed-content-warnings/163727>\
**Category:** Product Support\
**Created:** [September 11, 2020, 10:01am UTC](https://meta.discourse.org/t/mixed-content-warnings/163727 "2020-09-11T10:01:27Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![JuergenAuer](https://avatars.discourse-cdn.com/v4/letter/j/bb73d2/32.png) [@JuergenAuer](https://meta.discourse.org/u/JuergenAuer)\
**Post date:** [September 11, 2020, 12:40pm UTC](https://meta.discourse.org/t/mixed-content-warnings/163727/5 "2020-09-11T12:40:02Z")

</div>

> [@dax](#):
>
> The warning is nothing to worry about.

Mixed content warnings are always bad. It’s possible to add cookies via http that are used with the next https connection. So forum software should never initiate http connections.

Especially in a forum that talks about “My certificate is wrong” or “I have content warnings” (certificate is correct, but there is mixed content - first certificate with that domain, links must be updated).

---

_[View the full topic](https://meta.discourse.org/t/mixed-content-warnings/163727)._