3 ms·
After clicking through several more times and ending up in a gitlab wiki, this seems to be how it works: > It comes bundled with a fair amount of commonly use
by WJW 6y ago
After clicking through several more times and ending up in a gitlab wiki, this seems to be how it works:
> It comes bundled with a fair amount of commonly used files, and serves them locally whenever a site tries to fetch them from a delivery network.
The docs, both on the site that is linked to and on the wiki is extremely bare bones, but the gist of it is that a CDN can track you through the `referer` header of the request for (say) jquery, since even if the browser has jquery already cached it will send out a request to check if the resource might have been modified.
- paulryanrogers 6y agoWould a simpler solution be to just drop referrers from CDN requests? It would probably require fewer updates to the package itself
- kreetx 6y agoI'm not disagreeing, but without a referrer the request would go out anyway - with decentraleyes it doesn't at all.
- surround 6y agoDecentraleyes already does this. > What does it do to protect me when it has no choice but to allow a request? > Even if a resource is not locally available, Decentraleyes offers improved protection by stripping optional headers from intercepted CDN-requests. This keeps specific data, such as what page you are on, from reaching delivery networks. Whitelisting a domain does not affect this measure. https://git.synz.io/Synzvato/decentraleyes/-/wikis/Frequently-Asked-Questions#what-does-it-do-to-protect-me-when-it-has-no-choice-but-to-allow-a-request https://git.synz.io/Synzvato/decentraleyes/-/wikis/Frequentl...
- coronadisaster 6y agoThey can also track you by IP and other means... It is better to avoid CDNs if you can (mostly because they are so popular and centralized).
- m463 6y agoI had a friend who worked at a CDN and they are basically huge tracking networks.