News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Kevin Schroeder:
Why you should not use .htaccess (AllowOverride All) in production
February 25, 2013 @ 10:31:09

Kevin Schroeder has posted the results of some research he did around using the "AllowOverride" setting in Apache. He found some interesting differences when it was set to "all".

Commonly known as .htaccess, AllowOverride is a neat little feature that allows you to tweak the server's behavior without modifying the configuration file or restarting the server. [...] Beyond the obvious security problems of allowing configuration modifications in a public document root there is also a performance impact. What happens with AllowOverride is that Apache will do an open() call on each parent directory from the requested file onward.

He includes the output from a strace call in the post - first showing the function calls with it set to "none" then the same request with the setting on "all". More "open" calls are being made in the second run, increasing the execution time by a decent amount.

0 comments voice your opinion now!
apache allowoverride all htaccess production setting performance


blog comments powered by Disqus

Similar Posts

John Cox\'s Blog: IIS / Apache $_SERVER Comparison (cheatsheet)

Community News: Windows Software Tools for PHP Wants Beta Testers

phpRiot.com: Creating search engine friendly URLs in PHP

Christopher Jones' Blog: Oracle & PHP Users: don't miss the Zend Conference

Chris Jones: Converting REF CURSOR to PIPE for Performance in PHP OCI8 and PDO_OCI


Community Events





Don't see your event here?
Let us know!


podcast conference language voicesoftheelephpant tips list library laravel developer framework api series community interview introduction symfony release bugfix zendserver deployment

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework