Forum Moderators: phranque
Unfortunately, I can't replicate this problem on any of the computers I've tried, even after clearing the cache--so I'm working in the dark on this one.
In my htaccess files, I currently have:
# do not allow indexes
Options +FollowSymLinks -IndexesRewriteEngine on
RewriteCond %{HTTP_REFERER}!^$
RewriteCond %{HTTP_REFERER}!^http://(www\.)?myDomain.com/.*$ [NC]RewriteCond %{HTTP_REFERER}!^http://216\.239\.(3[2-9]¦[45][0-9]¦6[0-3]).*(www\.)?myDomain\.com [NC]
RewriteCond %{HTTP_REFERER}!^http://babel.altavista.com/.*(www\.)?myDomain\.com [NC]
RewriteCond %{HTTP_REFERER}!^http://216\.243\.113\.1/cgi/
RewriteCond %{HTTP_REFERER}!^http://search.*\.cometsystems\.com/search.*(www\.)?myDomain\.com [NC]
RewriteCond %{HTTP_REFERER}!^http://.*searchhippo\.com.*(www\.)?myDomain\.com [NC]RewriteRule \.(gif¦jpg¦jpeg?¦png)$ - [NC,F]
I'm thinking I should try removing the "/.*$" at the end of:
RewriteCond %{HTTP_REFERER}!^http://(www\.)?myDomain.com/.*$ [NC]
Does that make sense?
What does the "/.*$" at the end of that line actually do?
I'm guessing it says: "any character (the period), any number of them (the *) at/to the end of the string (the $). If so, then that seems unnecessary and could be the culprit.
Do I have to worry about causing other problems if I remove the "/.*$"?