In my recent push to optimize the bandwidth-sucking on my site, I went through my access logs to try to rip out the hotlinkers. Some of the files that were in my top bandwidth users didn’t seem like they should be getting used that often! Most notably… my prom pictures?!?
So I fired up the log viewer; here are some excerpts:
71.48.106.151 - - [05/Mar/2006:18:08:51 -0500] "GET /photos/2005%20Prom%20with%20Kristen/prom.jpg HTTP/1.1" 200 61706 "http://profile.myspace.com/index.cfm?fuseaction=user.viewprofile&friendid=2376569" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)" "-"
68.47.34.249 - - [05/Mar/2006:20:36:14 -0500] "GET /photos/2005%20Prom%20with%20Kristen/dance.jpg HTTP/1.1" 200 71466 "http://profile.myspace.com/index.cfm?fuseaction=user.viewprofile&friendid=20532237" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; (R1 1.5); .NET CLR 1.1.4322)" "-"This continued for pages. Dozens of people on MySpace hotlinking to my prom pictures! I couldn’t really even figure out why… comments ranged from “{naked Barbie picture} + {my prom picture} = happy” to “Look at this prom picture of me! {my prom picture}”.
Obviously, it’s because Kristen is gorgeous and all the little MySpace peons wanted to pretend that they looked like her / dated her. But don’t hotlink her! I did notice that I’m on the first page of Google Image Search for ‘prom’. I guess that’s partially the culprit.
I started off by just blocking the three or four worst-offending sites. MySpace, some photo-sharing site, and a couple foreign sites. The prom picture alone pulled over 300MB of bandwidth by itself, and Cao pulled another couple hundred. Rawr
Read the rest of this thought »