RewriteEngine On - GoFuckYourself.com

spacedog · 02-11-2006, 01:50 AM

when writing htaccess, does it get fucked up if RewriteEngine On is there more than once?

I want to add some things to my htaccess, but wordpress takes up a big portion of it, so, I leave that part alone & edit the other parts that are there before the wordpress shit.

Anyway, I need to add something that requires RewriteEngine On , but it's already on via the wordpress codes, so, do I put it there twice?

so, basically, I have my error documents, that dont require any mod, then after starts the wordpress shit & it starts with;

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On

so, if I am adding to this, I am putting it after the error document & before the # Begin wordpress

would this be incorrect;

RewriteEngine On
blah blah blah bullshit here
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On

or, do I put it there without RewriteEngine On, because it's on further down the page from wordpress??

Ok, I confused myself

spacedog · 02-11-2006, 02:01 AM

or when several parts require rewrite on? Does it only need rewrite on once, or for each part?

like;
RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www\.)?mydomain.com/.*$ [NC]
RewriteRule \.(gif|jpg|js|css)$ - [F]
RewriteEngine on
# Options +FollowSymlinks
RewriteCond %{HTTP_REFERER} badsite\.com [NC]
RewriteRule .* - [F]
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On

or should the RewriteEngine On only be there once? like this;
RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www\.)?mydomain.com/.*$ [NC]
RewriteRule \.(gif|jpg|js|css)$ - [F]
# Options +FollowSymlinks
RewriteCond %{HTTP_REFERER} badsite\.com [NC]
RewriteRule .* - [F]
# BEGIN WordPress
<IfModule mod_rewrite.c>

Tempest · 02-11-2006, 02:55 AM

You just need it once.

And what's that IfModule crap? You shouldn't need that unless it's in the apache server config. You either have mod_rewrite or you don't and you shouldn't need ot be checking it in your htaccess.

And any time you finish a "section" with your RewriteRule, you should put a "(L)ast flag in there.

RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www\.)?mydomain.com/.*$ [NC]
RewriteRule \.(gif|jp?g|bmp|png|js|css)$ - [NC,F,L]
RewriteCond %{HTTP_REFERER} badsite\.com [NC]
RewriteRule .* - [F,L]

spacedog · 02-11-2006, 03:02 AM

so then this is wrong then?

Code:

<Files .htaccess>
order allow,deny
deny from all
</Files>
RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www\.)?xxxwebmastersresources.com/.*$ [NC]
RewriteRule \.(gif|jpg|js|css)$ - [F]
ErrorDocument 400 http://www.xxxwebmastersresources.com
ErrorDocument 401 http://www.xxxwebmastersresources.com
ErrorDocument 403 http://www.xxxwebmastersresources.com
ErrorDocument 404 http://www.xxxwebmastersresources.com
ErrorDocument 500 http://www.xxxwebmastersresources.com
RewriteEngine On 
RewriteCond %{HTTP_USER_AGENT} ^BlackWidow [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Bot\ mailto:[email protected] [OR] 
RewriteCond %{HTTP_USER_AGENT} ^ChinaClaw [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Custo [OR] 
RewriteCond %{HTTP_USER_AGENT} ^DISCo [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Download\ Demon [OR] 
RewriteCond %{HTTP_USER_AGENT} ^eCatch [OR] 
RewriteCond %{HTTP_USER_AGENT} ^EirGrabber [OR] 
RewriteCond %{HTTP_USER_AGENT} ^EmailSiphon [OR] 
RewriteCond %{HTTP_USER_AGENT} ^EmailWolf [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Express\ WebPictures [OR] 
RewriteCond %{HTTP_USER_AGENT} ^ExtractorPro [OR] 
RewriteCond %{HTTP_USER_AGENT} ^EyeNetIE [OR] 
RewriteCond %{HTTP_USER_AGENT} ^FlashGet [OR] 
RewriteCond %{HTTP_USER_AGENT} ^GetRight [OR] 
RewriteCond %{HTTP_USER_AGENT} ^GetWeb! [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Go!Zilla [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Go-Ahead-Got-It [OR] 
RewriteCond %{HTTP_USER_AGENT} ^GrabNet [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Grafula [OR] 
RewriteCond %{HTTP_USER_AGENT} ^HMView [OR] 
RewriteCond %{HTTP_USER_AGENT} HTTrack [NC,OR] 
RewriteCond %{HTTP_USER_AGENT} ^Image\ Stripper [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Image\ Sucker [OR] 
RewriteCond %{HTTP_USER_AGENT} Indy\ Library [NC,OR] 
RewriteCond %{HTTP_USER_AGENT} ^InterGET [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Internet\ Ninja [OR] 
RewriteCond %{HTTP_USER_AGENT} ^JetCar [OR] 
RewriteCond %{HTTP_USER_AGENT} ^JOC\ Web\ Spider [OR] 
RewriteCond %{HTTP_USER_AGENT} ^larbin [OR] 
RewriteCond %{HTTP_USER_AGENT} ^LeechFTP [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Mass\ Downloader [OR] 
RewriteCond %{HTTP_USER_AGENT} ^MIDown\ tool [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Mister\ PiX [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Navroad [OR] 
RewriteCond %{HTTP_USER_AGENT} ^NearSite [OR] 
RewriteCond %{HTTP_USER_AGENT} ^NetAnts [OR] 
RewriteCond %{HTTP_USER_AGENT} ^NetSpider [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Net\ Vampire [OR] 
RewriteCond %{HTTP_USER_AGENT} ^NetZIP [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Octopus [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Offline\ Explorer [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Offline\ Navigator [OR] 
RewriteCond %{HTTP_USER_AGENT} ^PageGrabber [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Papa\ Foto [OR] 
RewriteCond %{HTTP_USER_AGENT} ^pavuk [OR] 
RewriteCond %{HTTP_USER_AGENT} ^pcBrowser [OR] 
RewriteCond %{HTTP_USER_AGENT} ^RealDownload [OR] 
RewriteCond %{HTTP_USER_AGENT} ^ReGet [OR] 
RewriteCond %{HTTP_USER_AGENT} ^SiteSnagger [OR] 
RewriteCond %{HTTP_USER_AGENT} ^SmartDownload [OR] 
RewriteCond %{HTTP_USER_AGENT} ^SuperBot [OR] 
RewriteCond %{HTTP_USER_AGENT} ^SuperHTTP [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Surfbot [OR] 
RewriteCond %{HTTP_USER_AGENT} ^tAkeOut [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Teleport\ Pro [OR] 
RewriteCond %{HTTP_USER_AGENT} ^VoidEYE [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Web\ Image\ Collector [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Web\ Sucker [OR] 
RewriteCond %{HTTP_USER_AGENT} ^WebAuto [OR] 
RewriteCond %{HTTP_USER_AGENT} ^WebCopier [OR] 
RewriteCond %{HTTP_USER_AGENT} ^WebFetch [OR] 
RewriteCond %{HTTP_USER_AGENT} ^WebGo\ IS [OR] 
RewriteCond %{HTTP_USER_AGENT} ^WebLeacher [OR] 
RewriteCond %{HTTP_USER_AGENT} ^WebReaper [OR] 
RewriteCond %{HTTP_USER_AGENT} ^WebSauger [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Website\ eXtractor [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Website\ Quester [OR] 
RewriteCond %{HTTP_USER_AGENT} ^WebStripper [OR] 
RewriteCond %{HTTP_USER_AGENT} ^WebWhacker [OR] 
RewriteCond %{HTTP_USER_AGENT} ^WebZIP [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Wget [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Widow [OR] 
RewriteCond %{HTTP_USER_AGENT} ^WWWOFFLE [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Xaldon\ WebSpider [OR] 
RewriteCond %{HTTP_USER_AGENT} ^Zeus 
RewriteRule ^.* - [F,L]
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^.*$ - [S=65]
deleted this because it's just all wordpress shit
</IfModule>

# END WordPress

spacedog · 02-11-2006, 03:03 AM

oh, the <IfModule mod_rewrite.c> is part of wordpress so that wordpress can write to the htaccess, at least that's what I think it is.

Tempest · 02-11-2006, 03:14 AM

Truth be told, I don't think it matters whether or not the "on" is there more than once.. I've had that there by mistake myself before and it didn't cause any problems.

You could put all your stuff after the wordpress commands and that way it will already be on.

The <IfModule></IfModule> is so that the commands within it are only executed if the mod_rewrite module is installed on apache. Since you know it is, it's not really required but won't hurt anything either.

I don't see any glaring problems with what you have. It's not as "clean" as I'd try and make it but it should work fine.

spacedog · 02-11-2006, 03:22 AM

thank you for your help.

02-11-2006, 01:50 AM	#1
spacedog Yes that IS me. Bitch. Industry Role: Join Date: Nov 2001 Posts: 14,149	RewriteEngine On when writing htaccess, does it get fucked up if RewriteEngine On is there more than once? I want to add some things to my htaccess, but wordpress takes up a big portion of it, so, I leave that part alone & edit the other parts that are there before the wordpress shit. Anyway, I need to add something that requires RewriteEngine On , but it's already on via the wordpress codes, so, do I put it there twice? so, basically, I have my error documents, that dont require any mod, then after starts the wordpress shit & it starts with; # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On so, if I am adding to this, I am putting it after the error document & before the # Begin wordpress would this be incorrect; RewriteEngine On blah blah blah bullshit here # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On or, do I put it there without RewriteEngine On, because it's on further down the page from wordpress?? Ok, I confused myself

02-11-2006, 02:01 AM	#2
spacedog Yes that IS me. Bitch. Industry Role: Join Date: Nov 2001 Posts: 14,149	or when several parts require rewrite on? Does it only need rewrite on once, or for each part? like; RewriteEngine on RewriteCond %{HTTP_REFERER} !^$ RewriteCond %{HTTP_REFERER} !^http://(www\.)?mydomain.com/.$ [NC] RewriteRule \.(gif\|jpg\|js\|css)$ - [F] RewriteEngine on # Options +FollowSymlinks RewriteCond %{HTTP_REFERER} badsite\.com [NC] RewriteRule . - [F] # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On or should the RewriteEngine On only be there once? like this; RewriteEngine on RewriteCond %{HTTP_REFERER} !^$ RewriteCond %{HTTP_REFERER} !^http://(www\.)?mydomain.com/.$ [NC] RewriteRule \.(gif\|jpg\|js\|css)$ - [F] # Options +FollowSymlinks RewriteCond %{HTTP_REFERER} badsite\.com [NC] RewriteRule . - [F] # BEGIN WordPress <IfModule mod_rewrite.c>

02-11-2006, 02:55 AM	#3
Tempest Too lazy to set a custom title Industry Role: Join Date: May 2004 Location: West Coast, Canada. Posts: 10,217	You just need it once. And what's that IfModule crap? You shouldn't need that unless it's in the apache server config. You either have mod_rewrite or you don't and you shouldn't need ot be checking it in your htaccess. And any time you finish a "section" with your RewriteRule, you should put a "(L)ast flag in there. RewriteEngine on RewriteCond %{HTTP_REFERER} !^$ RewriteCond %{HTTP_REFERER} !^http://(www\.)?mydomain.com/.$ [NC] RewriteRule \.(gif\|jp?g\|bmp\|png\|js\|css)$ - [NC,F,L] RewriteCond %{HTTP_REFERER} badsite\.com [NC] RewriteRule . - [F,L]

02-11-2006, 03:03 AM	#5
spacedog Yes that IS me. Bitch. Industry Role: Join Date: Nov 2001 Posts: 14,149	oh, the <IfModule mod_rewrite.c> is part of wordpress so that wordpress can write to the htaccess, at least that's what I think it is.

02-11-2006, 03:14 AM	#6
Tempest Too lazy to set a custom title Industry Role: Join Date: May 2004 Location: West Coast, Canada. Posts: 10,217	Truth be told, I don't think it matters whether or not the "on" is there more than once.. I've had that there by mistake myself before and it didn't cause any problems. You could put all your stuff after the wordpress commands and that way it will already be on. The <IfModule></IfModule> is so that the commands within it are only executed if the mod_rewrite module is installed on apache. Since you know it is, it's not really required but won't hurt anything either. I don't see any glaring problems with what you have. It's not as "clean" as I'd try and make it but it should work fine.

02-11-2006, 03:22 AM	#7
spacedog Yes that IS me. Bitch. Industry Role: Join Date: Nov 2001 Posts: 14,149	thank you for your help.