Ask HN: How can I protect myself from Referer tracking?
But when I check the network traffic, I see that it still sends the Referer and the Origin headers to the massive amounts of CDNs, mostly .googleapis.com, .gstatic.com and their army of bloat.
Google seem to put the cache headers already expired to make sure that it is notified on every page I visit no matter if the scripts were changed or not.
Obviously they do not need cookies to track my session because it is very easy to fingerprint a browser using only meta-data, or simply just the IP, which makes Privacy Badger seem really really useless.
I rarely see anybody mention this issue, and even search engines gives me little to no results.
My current idea of a solution would be to create a FF extension which holds a list of the tracking domain and simply prevents the Referer header from being sent. But there is also the Origin header, and also the issue with trusting Google altogether.
If they see that the request headers are unusual, they might aswell just respond with a whole other script altogether to further their tracking, or target the browsing session aggressively.
I suppose I could set up a mirror of all these CDNs and monitor them for changes.
Am I missing something? Are there any current extensions that prevent this?
Any network setup maybe with a caching proxy of some sort in the middle?
How can it be prevented?
0 comments
[ 2.8 ms ] story [ 14.8 ms ] threadNo comments yet.