Quote:
Originally Posted by BAILOPAN
Kyle12: Another webserver is an option, but we have a lot of custom apache gunk including .htaccess usage that we'd have to make sure can be ported first.
|
This might seem like nit picking but wouldn't you be better off using httpd.conf rather than .htaccess, as the Apace Foundation recommend? I know a lot of people ignore this advice but the problem supposedly scales severely. Its not just that apache needs to read .htaccess file every time, it needs to check each parent folder as well.
You can use includes within httpd.conf so you may be able to turn your existing .htaccess files into includes over time and perhaps even use user/group permissions on them for access control if needed. The only drawback I can think of (not having a great understanding of your setup) is that a root user needs to reload the conf for any changes to take effect. I understand this can be done 'gracefully' and does not require a complete apache restart. I don't have any real experience with this myself. I've used apache2 a little.
Its great you came back so well by the way. I was thinking about those Autumn leaves in Monty Pythons 'Meaning of Life'.