The Oprano Challenge Part 2

[Lee]

The contest:

Anti-Hotlinking .htaccess file for bunnypancake.com that stops hotlinking of the bunnypancake.jpg pic in the root whilst still allowing http://www.bunnypancake.com to access the image.

At the same time, if the pic is hotlinked, it should display bunny.jpg located on the domain root.

The prize:

$10 by paypal / epass.

[Lee]

Additional info:

See this thread for a bunch of .htaccess files that dont work:

http://www.oprano.com/msgboard/index.php?showtopic=19015

[sarettah]

Originally posted by Lee@Jun 16 2005, 07:41 PM
Additional info:

See this thread for a bunch of .htaccess files that dont work:

http://www.oprano.com/msgboard/index.php?showtopic=19015
They would have if you had explained properly what you really wanted dammit...

How come with every client you have to give them what they ask for before you find out what they want :headwall: :headwall:


this should work just fine. You can figure out all the various cases yourself :nyanya:

AuthUserFile /dev/null
AuthGroupFile /dev/null

RewriteEngine On

RewriteCond %{HTTP_REFERER} !^http://www.bunnypancake.com/.*$ [NC]
RewriteCond %{HTTP_REFERER} !^http://www.bunnypancake.com:80/.*$ [NC]
RewriteCond %{HTTP_REFERER} !^http://bunnypancake.com/.*$ [NC]
RewriteCond %{HTTP_REFERER} !^http://bunnypancake.com:80/.*$ [NC]

ReWriteRule .*\bunnypancake.jpg$ http://www.bunnypancake.com/bunny.jpg [R,L]

[Lee]

Originally posted by sarettah+Jun 16 2005, 08:06 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (sarettah @ Jun 16 2005, 08:06 PM)</td></tr><tr><td id='QUOTE'> <!--QuoteBegin-Lee@Jun 16 2005, 07:41 PM
Additional info:

See this thread for a bunch of .htaccess files that dont work:

http://www.oprano.com/msgboard/index.php?showtopic=19015
They would have if you had explained properly what you really wanted dammit...

How come with every client you have to give them what they ask for before you find out what they want :headwall: :headwall:


this should work just fine. You can figure out all the various cases yourself :nyanya:

AuthUserFile /dev/null
AuthGroupFile /dev/null

RewriteEngine On

RewriteCond %{HTTP_REFERER} !^http://www.bunnypancake.com/.*$ [NC]
RewriteCond %{HTTP_REFERER} !^http://www.bunnypancake.com:80/.*$ [NC]
RewriteCond %{HTTP_REFERER} !^http://bunnypancake.com/.*$ [NC]
RewriteCond %{HTTP_REFERER} !^http://bunnypancake.com:80/.*$ [NC]

ReWriteRule .*\bunnypancake.jpg$ http://www.bunnypancake.com/bunny.jpg [R,L] [/b][/quote]
Well its online lets see if it works ;)

http://www.bunnypancake.com/bunnypancake.jpg

[Lee]

WOO HOO!

We have a winner :rokk:

Sare if you want that Epass / paypal just shoot me a PM with your info, a deal is a deal afterall :okthumb:

[Newton]

Where was the two week's clause?

[Trev]

All the .htaccess that was posted in that thread works for me... you've either got cocksucker hosting or you can't cut and paste :P

[sarettah]

Originally posted by Lee@Jun 17 2005, 12:58 AM
Sare if you want that Epass / paypal just shoot me a PM with your info, a deal is a deal afterall :okthumb:
I don't need the paypal...lolol...

But, not to make an example (but gonna anyway) here is what I am talking about.

What you asked for in the other thread was:

That sucker has been posted on around 20 different forums in the last 12 hours LMAO

How do i change it [the htaccess] so that instead of just showing a blank image, it redirects to a different image?

All of the examples I saw in the other thread did that. Some based on referers, some based on image name. They all did a redirect to a different image of some sort.

In this thread you described it as:

Anti-Hotlinking .htaccess file for bunnypancake.com that stops hotlinking of the bunnypancake.jpg pic in the root whilst still allowing http://www.bunnypancake.com to access the image.

At the same time, if the pic is hotlinked, it should display bunny.jpg located on the domain root.


This was a more detailed request and described much more accurately what you wanted. The first request ASSUMED that we knew what your .htaccess looked like to begin with.

Once I had the 2nd request it was easy to do exactly what you wanted (actually just took the most basic image protection I had and made it specific to the image you wanted to protect)


With programmers you usually get exactly what you ask for, so you got to make sure what you ask for is actually what you want, otherwise you will go through several rounds of "Those fucking programmers" as they spend their two weeks building what you asked for, then spending more time building what you wanted :blink:

[TheEnforcer]

Hahahaha.. great post Sare...

:pearl: