From 5b56d06a01a150fc9685e6f913774be3f9deb49f Mon Sep 17 00:00:00 2001 From: Stefan Fritsch Date: Tue, 27 Dec 2011 19:43:09 +0100 Subject: Upstream tarball 2.2.19 --- docs/manual/howto/htaccess.html.en | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) (limited to 'docs/manual/howto/htaccess.html.en') diff --git a/docs/manual/howto/htaccess.html.en b/docs/manual/howto/htaccess.html.en index 95a5fef9..23fab6ce 100644 --- a/docs/manual/howto/htaccess.html.en +++ b/docs/manual/howto/htaccess.html.en @@ -19,6 +19,7 @@ Apache > HTTP Server > Documentation > Version 2.2 > How-To / Tutorials

Apache Tutorial: .htaccess files

Available Languages:  en  | + fr  |  ja  |  ko  |  pt-br 

@@ -39,7 +40,13 @@ changes on a per-directory basis.

top

.htaccess files

-
Related ModulesRelated Directives
+
Related ModulesRelated Directives
+ +
You should avoid using .htaccess files completely if you have access to + httpd main server config file. Using .htaccess files slows down your Apache server. + Any directive that you can include in a .htaccess file is + better set in a Directory block, + as it will have the same effect with better performance.
top

What they are/How to use them

@@ -120,7 +127,7 @@ changes on a per-directory basis.

However, in general, use of .htaccess files should be avoided when possible. Any configuration that you would consider putting in a .htaccess file, can just as effectively be - made in a <Directory> section in your main server + made in a <Directory> section in your main server configuration file.

There are two main reasons to avoid the use of @@ -376,10 +383,11 @@ Options +IncludesNoExec -ExecCGI

Available Languages:  en  | + fr  |  ja  |  ko  |  pt-br 

\ No newline at end of file -- cgit v1.2.3