4 ms·
The problem with caching is that you're sharing the referer with the canonical URL. Another problem is that you're using someone else's bandwidth. And if you co
by d33 11y ago
The problem with caching is that you're sharing the referer with the canonical URL. Another problem is that you're using someone else's bandwidth. And if you combine the two, you can be sure that info about your visitors will be sold, which is why quite a lot of people would prefer to host their own versions of jQuery...
- lolive 11y agoCouldn't the HTTP cache of your ISP be a good in-betweener, in that case? Would he send the referer to the canonical URL?
- mdavidn 11y agoNot for sites using TLS. The only option for secure sites would be a CDN. That is, an HTTP cache in a relationship with the content publisher rather than the subscriber.
- kevincox 11y agoFor the referrer problem you can apply a referrer policy to prevent this but unfortunately the referrer policy isn't very granular. Also for my sites I have a fallback to a local copy of the script. This allows me to do completely local development and remain up if the public CDN goes down (or gets compromised). With small (usually) performance impact.