2 ms·
Care to explain yourself? All using a CDN for JS libraries does is have the same exact code get to the user faster and not eat your bandwith. Unless the CDN th
by jackowayed 17y ago
Care to explain yourself?
All using a CDN for JS libraries does is have the same exact code get to the user faster and not eat your bandwith. Unless the CDN threw some extra code in, which someone would eventually notice (seriously marring the company's reputation), it doesn't send any info to the company hosting the code.
But it is a good point. You should make sure you really trust the company hosting the code for you.
Edit: Oh, right. When I read the comment I was thinking more of it letting them steal all of the info on the page, or something, which would be doable if they inserted extra code.
- Willie_Dynamite 17y agoYou've never heard of access logs?
- harpastum 17y agoI think the OP's point was that you're giving all of the traffic information to the CDN, i.e. they can monitor the people that you're sending to them.
- pyre 17y ago> Edit: Oh, right. When I read the comment I was thinking more of it letting them steal all of the info on the page, or something, which would be doable if they inserted extra code. Stealing info from the page is still possible. It would be hard to crowd-source the detection of such things if they were either: 1) randomly inserted into <1% of all requests; 2) they were targeted at specific IPs/IP ranges; or 3) they were targeted at requests coming from specific sites.