Straylight Run » htaccess http://blog.straylightrun.net Software, Technology, PHP Wed, 25 Apr 2012 16:11:41 +0000 en hourly 1 http://wordpress.org/?v=3.3.2 Tip Of The Day: Removing .htaccesshttp://blog.straylightrun.net/2009/06/17/tip-of-the-day-removing-htaccess/ http://blog.straylightrun.net/2009/06/17/tip-of-the-day-removing-htaccess/#comments Wed, 17 Jun 2009 20:48:21 +0000 gerard http://blog.straylightrun.net/?p=205 At work, every project has an .htaccess file containing at the least some mod_rewrite rules.  This way, all I need to do to run a project is check it out of version control.  I don’t need to modify my local Apache configuration.

But turning this option on and allowing .htaccess files may be a performance hit. More specifically, enabling the AllowOverride option in Apache is a performance hit. The Apache docs sums up the problem best:

“Wherever in your URL-space you allow overrides (typically .htaccess files) Apache will attempt to open .htaccess for each filename component. For example,

1
2
3
4

DocumentRoot /www/htdocs
<Directory />
   AllowOverride all
</Directory>

and a request is made for the URI /index.html. Then Apache will attempt to open /.htaccess, /www/.htaccess, and /www/htdocs/.htaccess.”

So I disabled all .htaccess files in production, and inserted each file’s individual mod_rewrite rules into the main Apache config file. After a quick Apache Bench run, one project looked around 3% faster. Note that there are a few other useful optimizations on that page.

]]> http://blog.straylightrun.net/2009/06/17/tip-of-the-day-removing-htaccess/feed/ 2