.htaccess vs. httpd.conf
-
-
- Cason
- Jr. Rocketeer
- Posts: 27
- Thanks: 0
-
In the past I read in several places that when having a dedicated server it is better to use the
server's httpd.conf file for configuration and not .htaccess.
In the performance regard, I understand that the reason is that it's better to avoid using .htaccess
if you can (if you have access to the httpd.conf on a dedicated server) because if you do use
.htaccess the downside is that with every http request made there are additional file system accesses for parent directories to check if they also hold .htacess files. and that results in some performance loss that could be avoided if you could use only httpd.conf without using .htaccess.
Now I'm setting up a managed dedicated server with a host (1and1) that would not allow me on a managed server to access files in the root directory where httpd.conf sits, so I know I won't be able to configure that file (and even if I could, since it's a managed dedicated server, that file would anyhow be overwritten daily by the host, because they manage the system files).
So I'm back again to using .htaccess and not htppd.conf.
My question to those who have the knowledge in this issue is:
Does it really matter so much and significantly affects the performance of a heavy traffic website if
you are using .htaccess (instead of just htppd.conf) or is the difference realy insignificant and shouldn't cause any noticable delay time in viewing webpages or noticable performance issues, even on a heavy traffic website?
-
Time to create page: 0.090 seconds