# 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:** 1\
**Showing post:** 46

<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>

---

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