cdn-enterprise.discourse.org's DNT policy not being recognized

[mpalmer]

This is a follow-on to EFForg/privacybadgerfirefox-legacy#490

We've just got another report of problems: https://twitter.com/flobin/status/816726049748910080

I cannot reproduce this issue myself: Privacy Badger considers cdn-enterprise.discourse.org to be quite well behaved on my system.

The CDN being blocked (cdn-enterprise.discourse.org) sets no cookies and does not modify local storage. The site that reports the problems is https://discourse.mcneel.com; other sites that also use that same CDN domain include https://bbs.boingboing.net/, https://twittercommunity.com/, and https://forums.docker.com/, all of which are working fine for me.

I'd really appreciate some indication of what Privacy Badger is considering to be inappropriate about cdn-enterprise.discourse.org's behaviour, so we can fix it.

[cooperq]

le'sigh. cnd-enterprise.discourse.org is being correctly marked as supporting DNT for me (and therefore not being blocked.) @mpalmer is it being blocked for you? I would have to find a browser where this is happening to get more info about what is going on here.

[mpalmer]

It isn't being blocked for me. The screenshot in the tweet I linked to (included here, because links to dropbox are pants) looks like Chrome to me.

[screenshot redacted, see below]

I've also asked the person who reported the issue to chime in here, so hopefully they'll be able to give more detail about what their exact environment is.

[Flobin]

Hi everyone–this was indeed my screenshot. My browser is chrome 55.0.2883.95 on macOS Sierra 10.12.3. Other extensions include uBlock origin, WebRTC Leak Prevent, and HTTPS Everywhere. Maybe one of those extensions interfered with Privacy Badger. Here’s a cleaner screenshot that doesn’t include my email 😉

The same thing happens on https://bbs.boingboing.net/, https://twittercommunity.com/, and https://forums.docker.com/, by the way.

[alexristich]

@Flobin In your second screenshot it looks like you have a manually overriden setting for this domain. If you click the arrow on the right to revert it, does it still revert to being blocked?

@cooperq I can't check at the moment, but I wonder if there's a way to manually run the DNT recheck in case it's out of date?

[cooperq]

There is but I want to see if @Flobin clicks the arrow if that fixes the problem. I'm thinking it should. If not we will dig into storage and see when it is due to be rechecked.

[ghostwords]

I'm going to close this as I see Discourse's DNT policy get properly recognized:

Let me know if there is still an issue here.

[mpalmer]

@Flobin, as the original-reporter-via-proxy, is everything working OK for you now?

[Flobin]

@mpalmer Yep, looks like it works correctly now!

[mpalmer]

Yay! Thanks for the confirmation.