You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Privacy Badger sees a "PHPSESSID" cookie getting set by static.my.id resources and so picks it up as a tracker. Is there a reason for setting cookies from CDN domains? If you can keep your CDN domains cookie-free, Privacy Badger won't learn to block them in the future.
Alternatively, if static.my.id does not actually track users, it may be compliant with EFF's Do Not Track policy. If you posted EFF's DNT policy on the static.my.id domain, the policy file will tell Privacy Badgers to always allow resources from static.my.id.
Privacy Badger sees a "PHPSESSID" cookie getting set by static.my.id resources and so picks it up as a tracker. Is there a reason for setting cookies from CDN domains? If you can keep your CDN domains cookie-free, Privacy Badger won't learn to block them in the future.
The static.my.id domain is cookie-free. Apparently img.static.my.id that actually causes this "PHPSESSID" cookie issue, and I'm going to move all resources from that subdomain. Hopefully, this will resolve the issue.
Alternatively, if static.my.id does not actually track users, it may be compliant with EFF's Do Not Track policy. If you posted EFF's DNT policy on the static.my.id domain, the policy file will tell Privacy Badgers to always allow resources from static.my.id.
What is your browser and browser version?
Firefox 78.0.1
What is broken and where?
kawanua.id
And, every site using my CDN resources from the URL address below.
What is the "culprit" domain?
static.my.id
What is your debug output for this domain?
The text was updated successfully, but these errors were encountered: