|
|
Posted by Rik on 01/29/07 18:46
Blinky the Shark <no.spam@box.invalid> wrote:
>>> Is there any chance that's something that, say, cPanel might do if one
>>> were to enable hot-link blocking? Like perhaps it would only apply to
>>> image requests that didn't come from within the site?
>>>
>>> I seem to have an .htaccess in my images directory, as well.
>>>
>> There probably was a preceding line with a RewriteCond statement that
>> test if the host is your domain name.
>>
>> # IF referring is not "mydomain.com"
>> RewriteCond %{HTTP_REFERER} !^http://(www\.)?mydomain.com/.*$ [NC]
>>
>> Since you have an new domain your are testing you need to allow it... or
>> remove the rule entirely...
>
> Here's that part of my .htaccecss (the one in my document root:
>
> RewriteEngine on
> RewriteCond %{HTTP_REFERER} !^$
> RewriteCond %{HTTP_REFERER} !^http://blinkynet.net/.*$ [NC]
> RewriteCond %{HTTP_REFERER} !^http://blinkynet.net$ [NC]
> RewriteCond %{HTTP_REFERER} !^http://www.blinkynet.net/.*$ [NC]
> RewriteCond %{HTTP_REFERER} !^http://www.blinkynet.net$ [NC]
> #RewriteRule .*\.(jpg|jpeg|gif|png|bmp)$ - [F,NC]
> Looks sensible?
Well, the .htaccess in the root will also process all requests for the
images directory.
This is indeed clearly a rule to prevent hot-linking, allthough it could
be very shorter:
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www\.)?blinkynet.net(/|$) [NC]
RewriteRule \.(jpg|jpeg|gif|png|bmp)$ - [F]
> There's none of that in the .htaccess that's in my images subdirectory,
> and since there are lines like AddHandler and DefaultCharset in that one
> I sense it's a file that simply got mis-saved to the wrong place.
There's no way for us to tell how it got there, and what it's purpose was
:P
--
Rik Wasmus
Navigation:
[Reply to this message]
|