# Discourse CDNs are blocked by privacy badger

**URL:** <https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127>\
**Category:** Site feedback\
**Created:** [2014 年7 月 2 日 20:03 UTC](https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127 "2014-07-02T20:03:36Z")\
**Posts on this page:** 1\
**Showing post:** 38

<div class="post-metadata">

作者： ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
发布日期： [2016 年3 月 28 日 00:52 UTC](https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127/38 "2016-03-28T00:52:19Z")

</div>

Speaking entirely for myself, I find Cloudflare’s addition of a top-of-zone tracking cookie to be appalling behaviour. I thought they were one of the good guys, but this… not so much.

With my Discourse hat on, I’ve made the necessary changes to have `avatars.discourse.org` served via an alternate CDN (MaxCDN). I’ve verified that the responses now come back with no cookies whatsoever. If anyone sees any issues, or even if the Privacy Badger problems don’t abate, please respond in this topic.

---

_[View the full topic](https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127)._