4 ms·
Perhaps a little harsh. Is the problem bandwidth or connection quantity? If it's bandwidth then they should just 301 to the Google CDN.
by jasoncartwright 16y ago
Perhaps a little harsh. Is the problem bandwidth or connection quantity? If it's bandwidth then they should just 301 to the Google CDN.
- izak30 16y agoThey are not disabling their CDN. They are only disabling hotlinking against other sources. This was in the first sentence.
- jasoncartwright 16y agoI understand that. The question still stands - if it's a bandwidth problem on jquery.com, why not just 301 it somewhere else?
- zootm 16y agoBecause 301'ing provides little or no incentive for the offenders to do the right thing. Also it doesn't stop the excess traffic, it just reduces it.
- jeresig 16y agoStraight connection overloading. We're already redirecting the majority of the files - but somehow the hotlking continue to persist.
- jasoncartwright 16y agoMakes sense, good decision then.
- ronnier 16y agoHow are you preventing hotlinking while still allowing the files to function normally on jquery.com? Inspecting the referrer or checking to see if other resources were previously downloaded?
- kmfrk 16y agoYou can do it in your .htaccess file. Define some extensions that are blacklisted and redirect referrers outside your own domain to a place of your choice. CPanel allows you to do this directly (although you might want to back up your .htaccess file first).