Page 1 of 1
Enable .htaccess ?
Posted: Sun May 04, 2014 1:09 am
by Robotrono
Well, I have a fresh install VestaCP, my problem is .htaccess dont work, how enable this?
I need change the extension from a file php to png with .htaccess
Re: Enable .htaccess ?
Posted: Sun May 11, 2014 9:46 am
by JRJr
Nginx doesn't support .htaccess files.
.htaccess files are a resource/performance hog and this is not good for your website/server speed.
Every time Apache handles a request it first checks and processes any .htaccess file in the same directory as the file it is serving. Not everyone knows this but Apache also goes through all the parent directories, and in every single one of them it checks for .htaccess files.
Another issue with dynamic .htaccess files is the fact it is really insecure as it is providing a way to alter server and website settings from a single file that is located inside the home directory of each website. This won't happen if you have your rules inside your Nginx configuration, as only root permission is granted to access them.
.htaccess provides a convenient shortcut for the lazy admin or developer, but also kills performance, makes configuration issues more difficult to track down, and opens yet another attack vector on your site.
You're well rid of them.
Re: Enable .htaccess ?
Posted: Sat May 17, 2014 7:55 pm
by drMacFaulty
JRJr wrote:Nginx doesn't support .htaccess files.
.htaccess files are a resource/performance hog and this is not good for your website/server speed.
Every time Apache handles a request it first checks and processes any .htaccess file in the same directory as the file it is serving. Not everyone knows this but Apache also goes through all the parent directories, and in every single one of them it checks for .htaccess files.
Another issue with dynamic .htaccess files is the fact it is really insecure as it is providing a way to alter server and website settings from a single file that is located inside the home directory of each website. This won't happen if you have your rules inside your Nginx configuration, as only root permission is granted to access them.
.htaccess provides a convenient shortcut for the lazy admin or developer, but also kills performance, makes configuration issues more difficult to track down, and opens yet another attack vector on your site.
You're well rid of them.
If I want to disable .htaccess, all I need to do is change AllowOverride All to None in the template (.tpl) files, right?