From c9ea5a053fc6454617f3d3db9265ce823a90e284 Mon Sep 17 00:00:00 2001 From: Richard Bowen Date: Thu, 25 Jul 2002 19:10:17 +0000 Subject: [PATCH] Submitted by: Michael Schroepl Typos, grammar, and phrasing corrections. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96191 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/howto/htaccess.html | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/docs/manual/howto/htaccess.html b/docs/manual/howto/htaccess.html index 03d6ed7f60..5b22cbeef1 100755 --- a/docs/manual/howto/htaccess.html +++ b/docs/manual/howto/htaccess.html @@ -18,15 +18,15 @@ @@ -105,9 +105,9 @@ FileInfo -

If you are unsure whether a particular diretive is permitted in a +

If you are unsure whether a particular directive is permitted in a .htaccess file, look at the documentation for that directive, and check - the Context line for ".htaccess"

+ the Context line for ".htaccess."

When (not) to use .htaccess files

@@ -141,9 +141,10 @@

Further note that Apache must look for .htaccess files in all higher-level directories, in order to have a full complement of - directives that it must apply. (See section on how directives are - applied, below.) Thus, if a file is requested out of a directory - /www/htdocs/example, Apache must look for the following files:

+ directives that it must apply. (See section on how + directives are applied.) Thus, if a file is requested out of + a directory /www/htdocs/example, Apache must look for the following + files:

/.htaccess
@@ -192,7 +193,7 @@ AddType text/example .exm AllowOverride None
-

How directives are applied:

+

How directives are applied

The configuration directives found in a .htaccess file are applied to the directory in which the .htaccess file is found, and to all @@ -201,7 +202,7 @@ AddType text/example .exm are applied in the order that they are found. Therefore, a .htaccess file in a particular directory may override directives found in .htaccess files found higher up in the directory tree. And those, in turn, may have - overriden directives found yet higher up, or in the main server + overridden directives found yet higher up, or in the main server configuration file itself.

Example:

@@ -224,7 +225,7 @@ Options Includes

Because of this second .htaccess file, in the directory - /www/htdocs/example1/example2, cgi execution is not permitted, as only + /www/htdocs/example1/example2, CGI execution is not permitted, as only Options Includes is in effect, which completely overrides any earlier setting that may have been in place.

@@ -263,7 +264,7 @@ Options Includes

Please see the authentication tutorial for a more complete discussion of authentication and authorization.

-

SSI example

+

Server side includes example

Another common use of .htaccess files is to enable Server Side Includes for a particular directory. This may be done with the following -- 2.40.0