Web Hosting Talk : Web Hosting Main Forums : VPS Hosting : place rewrite rules in .htaccess to virtual host config

[kurtk]

I want to eliminate the overhead of .htaccess by putting these rewrite rules

RewriteEngine On
RewriteCond %{REQUEST_FILENAME} -s [OR]
RewriteCond %{REQUEST_FILENAME} -l [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^.*$ - [NC,L]
RewriteRule ^.*$ index.php [NC,L]

in the virtual host configuration file. Do I just add DOCUMENT_ROOT like this?

RewriteEngine On
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_FILENAME} -s [OR]
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_FILENAME} -l [OR]
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_FILENAME} -d
RewriteRule ^.*$ - [NC,L]
RewriteRule ^.*$ index.php [NC,L]

[cloudrck]

What overhead are you experiencing? You should be fine with the .htaccess.

[foobic]

Originally Posted by kurtk

in the virtual host configuration file. Do I just add DOCUMENT_ROOT like this?

No, just use the same rules inside the virtualhost container that you would in the .htaccess file. When you're sure it's working, AllowOverride None in the main config file to disable .htaccess altogether.

daejuanj - the config files are read once, on Apache startup. .htaccess files (in the request directory and parent directories) are read on every single request. It's not much of an overhead for one or two rules in one .htaccess file but with larger rule sets or several files it adds up. If you have access to the config files, why not take advantage of it?

[cloudrck]

Originally Posted by foobic

daejuanj - the config files are read once, on Apache startup. .htaccess files (in the request directory and parent directories) are read on every single request. It's not much of an overhead for one or two rules in one .htaccess file but with larger rule sets or several files it adds up. If you have access to the config files, why not take advantage of it?

I'm aware of this, but like you said, it's not much for simple programming, I think most people over exaggerate their overhead without actually doing benchmarks. You do bring up a point, if I had access to the config files I would use it to.

I was curious if the OP actually knew the amount of overhead it were causing.

[kurtk]

Thanks for the replies. Are you sure about using

the same rules inside the virtualhost container that you would in the .htaccess file. When you're sure it's working

According to http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewriterule

The most visible change to look out for here is that in VirtualHost (per-server) context the request URI as seen by RewriteRule will start with a / (slash). Conversely in .htaccess or Directory (per-directory) the directory containing the rules, plus a trailing slash, are stripped before the comparison to the pattern.