From: Rich Bowen Date: Tue, 28 Sep 2010 11:29:30 +0000 (+0000) Subject: A few minor nitpicks. Removal of a double negative. Alteration of example X-Git-Tag: 2.3.9~403 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=b18ae22f5336c91adaea3e89a51b3aa30bb2ea52;p=thirdparty%2Fapache%2Fhttpd.git A few minor nitpicks. Removal of a double negative. Alteration of example using AllowOverride All in to use something less awful. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1002119 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/howto/htaccess.html.en b/docs/manual/howto/htaccess.html.en index 1e2b1a72015..2751ddd2dda 100644 --- a/docs/manual/howto/htaccess.html.en +++ b/docs/manual/howto/htaccess.html.en @@ -65,7 +65,7 @@ changes on a per-directory basis.

In general, .htaccess files use the same syntax as the main configuration - files. What you can put in these files is determined by the + files. What you can put in these files is determined by the AllowOverride directive. This directive specifies, in categories, what directives will be honored if they are found in a .htaccess file. If a @@ -100,7 +100,7 @@ changes on a per-directory basis.

When (not) to use .htaccess files

-

In general, you should never use .htaccess files unless +

In general, you should only use .htaccess files when you don't have access to the main server configuration file. There is, for example, a common misconception that user authentication should always be done in .htaccess files, and, in more recent years, @@ -259,14 +259,14 @@ changes on a per-directory basis.

As discussed in the documentation on Configuration Sections, .htaccess files can override the <Directory> sections for the corresponding directory, but will be overriden by other types - of configuration sections from the main configuration files. This + of configuration sections from the main configuration files. This fact can be used to enforce certain configurations, even in the - presence of a liberal AllowOverride setting. For example, to + presence of a liberal AllowOverride setting. For example, to prevent script execution while allowing anything else to be set in .htaccess you can use:

-<Directory />
+<Directory /www/htdocs>
Allowoverride All
 @@ -279,6 +279,8 @@ Options +IncludesNoExec -ExecCGI
</Location>

+
This example assumes that your DocumentRoot is /www/htdocs.
+
top
diff --git a/docs/manual/howto/htaccess.xml b/docs/manual/howto/htaccess.xml index 5406e2b1e3e..3ef18e95395 100644 --- a/docs/manual/howto/htaccess.xml +++ b/docs/manual/howto/htaccess.xml @@ -80,7 +80,7 @@ changes on a per-directory basis.

In general, .htaccess files use the same syntax as the main configuration - files. What you can put in these files is determined by the + files. What you can put in these files is determined by the AllowOverride directive. This directive specifies, in categories, what directives will be honored if they are found in a .htaccess file. If a @@ -122,7 +122,7 @@ changes on a per-directory basis.

When (not) to use .htaccess files -

In general, you should never use .htaccess files unless +

In general, you should only use .htaccess files when you don't have access to the main server configuration file. There is, for example, a common misconception that user authentication should always be done in .htaccess files, and, in more recent years, @@ -288,15 +288,15 @@ changes on a per-directory basis.

.htaccess files can override the Directory sections for the corresponding directory, but will be overriden by other types - of configuration sections from the main configuration files. This + of configuration sections from the main configuration files. This fact can be used to enforce certain configurations, even in the presence of a liberal AllowOverride setting. For example, to + module="core">AllowOverride setting. For example, to prevent script execution while allowing anything else to be set in .htaccess you can use:

-<Directory />
+<Directory /www/htdocs>
Allowoverride All
 @@ -308,6 +308,9 @@ Options +IncludesNoExec -ExecCGI
</Location> + + This example assumes that your DocumentRoot is /www/htdocs.
diff --git a/docs/manual/howto/htaccess.xml.ja b/docs/manual/howto/htaccess.xml.ja index d3a048676e8..84940ab75d5 100644 --- a/docs/manual/howto/htaccess.xml.ja +++ b/docs/manual/howto/htaccess.xml.ja @@ -1,7 +1,7 @@ - + + +