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

Symfony Project: Larger compatibility (magic_quotes_gpc)

Volker Dusch's Blog: References suck! - Let's fix MySqli prepared statements!

Tecmint.com: Install Apache, MySQL 5.5.27 & PHP 5.4.7 on RHEL/CentOS 6.3/5.6 & Fedora 17-12

Yahoo Developer Network: 'Tis the season for developers' calendars

PHPImpact Blog: Improving the performance of Zend_Controller


Community Events





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


framework list introduction code podcast install testing series symfony2 developer community laravel interview language refactor release threedevsandamaybe api unittest opinion

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