Re:Hotlinking to jquery.com will be disabled on January 31, ...
by jasoncartwright on Friday December 31, 2010 @10:22AM
(#2055560)
Perhaps a little harsh. Is the problem bandwidth or connection quantity? If it's bandwidth then they should just 301 to the Google CDN.
[ Parent
| on HN ]
Re:Hotlinking to jquery.com will be disabled on January 31, ...
by jeresig on Friday December 31, 2010 @10:30AM
(#2055578)
Straight connection overloading. We're already redirecting the majority of the files - but somehow the hotlking continue to persist.
Re:Hotlinking to jquery.com will be disabled on January 31, ...
by ronnier on Friday December 31, 2010 @10:47AM
(#2055620)
How 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?
Re:Hotlinking to jquery.com will be disabled on January 31, ...
by kmfrk on Friday December 31, 2010 @12:13PM
(#2055826)
You 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).
Re:Hotlinking to jquery.com will be disabled on January 31, ...
by jasoncartwright on Friday December 31, 2010 @10:31AM
(#2055583)
Makes sense, good decision then.
Re:Hotlinking to jquery.com will be disabled on January 31, ...
by izak30 on Friday December 31, 2010 @10:26AM
(#2055566)
They are not disabling their CDN. They are only disabling hotlinking against other sources. This was in the first sentence.
Re:Hotlinking to jquery.com will be disabled on January 31, ...
by jasoncartwright on Friday December 31, 2010 @10:29AM
(#2055577)
I understand that. The question still stands - if it's a bandwidth problem on jquery.com, why not just 301 it somewhere else?