# 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:** [7월 2, 2014, 8:03오후 UTC](https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127 "2014-07-02T20:03:36Z")
**Posts on this page:** 8
**Page:** 3

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [7월 17, 2016, 11:01오후 UTC](https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127/41 "2016-07-17T23:01:07Z")

</div>

I shall don my asbestos undergarments and wade in…

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [1월 5, 2017, 1:18오전 UTC](https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127/42 "2017-01-05T01:18:11Z")

</div>

Getting another report of this on Twitter:

 ![](https://global.discourse-cdn.com/meta/original/3X/f/c/fc81e8cb8c2b70b5899930a1edcc809d84241ced.jpg)

Apparently “everyone’s Privacy Badger will behave differently, based on what sites you’ve visited in the past” – can you elaborate on this @riking?

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [1월 5, 2017, 1:26오전 UTC](https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127/43 "2017-01-05T01:26:05Z")

</div>

Yep. Basically every time you visit a Cloudflare site, the heuristic sees “it’s sending/setting a long random cookie **to a domain 3rd-party vs the page** , that’s suspicious.” After a few visits, it transitions to red.

The fix would be to have special handling for \_\_cfuuid, e.g. locking just that cookie to the yellow area.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [1월 5, 2017, 1:28오전 UTC](https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127/44 "2017-01-05T01:28:20Z")

</div>

Is McNeel using CloudFlare? I didn’t think they were. We definitely don’t use it, except for the main website and blog. So why is `cdn-enterprise.discourse.org` – which has zilch to do with CloudFlare – getting tarred with this particular brush?

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [1월 5, 2017, 1:34오전 UTC](https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127/45 "2017-01-05T01:34:34Z")

</div>

They’re not using it anywhere I can see. I’ve also confirmed that there’s no cookies coming back on `cdn-enterprise.discourse.org`. I’m sticking with “Privacy Badger is… complicated”, and leaving this bug report here: [Issue · GitHub](https://github.com/EFForg/privacybadgerfirefox-legacy/issues/490)

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [1월 5, 2017, 1:36오전 UTC](https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127/46 "2017-01-05T01:36:05Z")

</div>

Oh, right. Hmmm… the `v` parameter maybe? That’d be a real pain if that’s what’s tripping it.

Here’s one of the relevant source files from last time I was investigating this stuff:

> <https://github.com/EFForg/privacybadgerfirefox-legacy/blob/master/lib/heuristicBlocker.js#L23>

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [1월 5, 2017, 1:43오전 UTC](https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127/47 "2017-01-05T01:43:15Z")

</div>

Since apparently the “legacy” issues aren’t being watched any more, I’ve just created [cdn-enterprise.discourse.org's DNT policy not being recognized · Issue #1121 · EFForg/privacybadger · GitHub](https://github.com/EFForg/privacybadger/issues/1121) to hopefully get some insight on this from the PB dev team.

---

<div class="post-metadata">

### Author: ![elijah](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elijah/32/104055_2.png) [@elijah](https://meta.discourse.org/u/elijah)
#### Post date: [8월 15, 2017, 2:02오전 UTC](https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127/48 "2017-08-15T02:02:35Z")

</div>

I see it happening again with the avatars host:

> [@Some sites are missing letter icons](https://meta.discourse.org/t/some-sites-are-missing-letter-icons/68027/4):
>
> It’s not FF55. It’s [Privacy Badger](https://www.eff.org/privacybadger). It has decided that [cdn.discourse.org](http://cdn.discourse.org) and [cdn-enterprise.discourse.org](http://cdn-enterprise.discourse.org) are safe, but that [avatars.discourse.org](http://avatars.discourse.org) is tracking me. The two CDN sites get a nice little DNT check box with “This domain promises to not track you” message, but avatars does not.

Took me a while to realize it was PB.

[이전 페이지](https://meta.discourse.org/t/discourse-cdns-are-blocked-by-privacy-badger/17127.md?page=2)
