Older Posts
· Difference between Trim$ and Trim in Visual Basic
· Which is worse, hotlinking or "stealing" images?
· How to print nonprinting characters in Microsoft W...
· New blog location
Archives
April 2005
May 2005
June 2005
July 2005
August 2005
November 2005
December 2005
January 2006
February 2006
March 2006
May 2006
June 2006
July 2006
August 2006
October 2006
March 2007
May 2007
June 2007
September 2007
November 2007
January 2008
June 2008
August 2008
Links
· Startup Applications List
· Welcome to the Hex Hub (Named Hexadecimal Color Codes for HTML)
More blogs on this site:
|
|
Computer Blog - thebroadroom.net: More on hotlinking
Disclaimer: all of the following is purely from personal experience. TheBroadroom.Net urges you to use your own instincts,
common sense, and willingness to take risks when applying any of the information below.
More on hotlinking
posted by Colleen Shirazi,
Wednesday, May 11, 2005
at 12:11 AM (Pacific)
Holy beejabbers! This is something that can literally wipe out smaller sites, in a hurry. Our own site stats were quickly being taken over by a single bandwidth-sucking demonic domain we shall call x.com.
My projections were that a.) we'd have no more site statistics by next month and b.) we'd lose all of our multi-gig bandwidth by the end of the year.
I spent a few days tooling around on the Net looking for answers. At first I had the idea of blocking x.com alone. I tried it out in several configurations but here is the best code I found:
.htaccess hotlinking prevention
This sweet snippet is, well, efficient and neat, and, what the hell. If it's x.com today, it's going to be y.com and z.com tomorrow.
I can admit I was skeptical about anti-hotlinking as a religion. I'm not religious. Again--want to stress this--the guy or gal who doesn't have his/her own server, and simply wants to show a picture on the fly, has never been the problem.
The problem are the bandwidth-draining vampire corporate sites like x.com. The users of x.com, either have no clue what they're doing, or else they just don't get it. I checked out Photobucket. Photobucket has a bandwidth limit and the users of x.com know that--because they've already maxed it out.
I hope this .htaccess thing works.
0 Comment(s)
 
|
