3 ms·
I think the author was pointing out that, if you put https://.../jquery.js https://.../jquery.js in your page and a visitor comes from a site using http://.../j
by JoachimSchipper 16y ago
I think the author was pointing out that, if you put https://.../jquery.js https://.../jquery.js in your page and a visitor comes from a site using http://.../jquery.js http://.../jquery.js, he'll have to re-download the file. (The HTTPS resource is cached, but the browser doesn't use the in-cache HTTP resource.)
- nolok 16y agoWhich is the correct way to do it. If the URI change, then the content can not be assumed to be identical. You can set up a server to serve two totally different websites on the same domain name, one on http and the other on https. If both those site have a javascript file of the same name at the same path, I certainly do not want my browser to confuse them. On top of that, that's not "crippling google's CDN caching" at all, that article is over exaggerating.
- JoachimSchipper 16y agoI agree with you on all points - I was just pointing out that the article did have some point.