# Endless loading behind Cloudflare

**URL:** https://meta.discourse.org/t/endless-loading-behind-cloudflare/364596
**Category:** Support
**Tags:** cloudflare
**Created:** [May 2, 2025, 10:18pm UTC](https://meta.discourse.org/t/endless-loading-behind-cloudflare/364596 "2025-05-02T22:18:04Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![MichaIng](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaing/32/251089_2.png) [@MichaIng](https://meta.discourse.org/u/MichaIng)
#### Post date: [May 11, 2025, 2:41am UTC](https://meta.discourse.org/t/endless-loading-behind-cloudflare/364596/15 "2025-05-11T02:41:34Z")

</div>

And another find: We use [`mod_sed`](https://httpd.apache.org/docs/current/mod/mod_sed.html) to add our Matomo tracker code to all `text/html` responses, right in front of the `</head>` end tag. Disabling it for Discourse (or bypassing the Apache2 proxy) solves things as well, despite Cloudflare Automatic HTTPS Rewrites active. To disabling either of both solves things. On all other pages the combination works fine, also on very large pages we have, larger than failing forum pages. So maybe the two filters, first `mod_set` on our proxy and then the embedded URL rewrites by Cloudflare cause something to break, related to document or chunk sizes or whatever.

We embed the tracker via Discourse theme edit now, and I additionally disabled the Cloudflare Automatic HTTPS Rewrites. There is no mixed content on our whole website. And if there is, good to see and fix it, instead of having Cloudflare masking it forever.

---

_[View the full topic](https://meta.discourse.org/t/endless-loading-behind-cloudflare/364596)._