httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Stuart <>
Subject Re[2]: rip-proofing content
Date Fri, 06 Jul 2001 14:14:46 GMT
Hello Daniel,

Thursday, July 05, 2001, 8:14:39 PM, you wrote:

DV> On Thu, Jul 05, 2001 at 05:15:35PM -0700, John E. Mayorga wrote:
>> I've thought of a couple of way I might be able to protect her content,
>> and I was hoping someone with a similar problem might offer some
>> suggestions.

DV>   Just a guess, it's a porn site, right ;-) ?

DV> Daniel

Daniel, what does that have to do with anything?  If anything, you should be
HAPPY that the majority of the adult websites out there use Apache?  We pull
MORE bandwidth PER day than most sites pull in a couple of months!  We
definitely STRESS test apache a LOT!!! Also, I'd like to point out three other

#1) The adult entertainment industry on the net has been about the only (if
not only) industry on the net to continue to make money throughout the slowing

#2) The adult entertainment industry is usually 6 months to 1 year AHEAD of
where the mainstream net is going to be.  QED you get a look at the future of
the net.

#3) Since people tend to like to download porn as quickly as possible, ISP's
and backbones keep expanding their pipe and therefore, we ALL benifit by
faster connections!

Anyway.. John, what you MIGHT be able to do is use htaccess to at least put
SOME kind of hotlinking protection in.

IE try this:

RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} !^Mozilla.*/
RewriteRule /*

Note, many site rippers can pretend to be a normal surfer so this might not
help as much as you would want... :(

Bout the only other thing I can think of is you can use something like
mod_throttle to throttle the bandwidth for each client therefore a cable modem
or DSL junkie will take as long to download the site as a 56ker would.  QED
they might give up.

Best regards,
 Jeff Stuart
 Internet Consultant for both Mainstream AND Adult

View raw message