From: Chris Pepper Date: Tue, 11 Dec 2001 01:49:46 +0000 (+0000) Subject: Fixed a few typos. X-Git-Tag: 2.0.30~234 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=d8fa8fb9db7f81f895c3bc37ff5cdc994823cc59;p=thirdparty%2Fapache%2Fhttpd.git Fixed a few typos. Fixed some HTML tags (case, href/name/id) Added a mention of multiple 'arguments' to allow/deny, and an example. This should probably be more explicit, but I'm not sure of the details (should we show with leading/trailing periods, and explain that IPs are assumed to be the left side, but hostnames are assumed to be the right side?). PR: Obtained from: Submitted by: Reviewed by: git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@92414 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/howto/auth.html b/docs/manual/howto/auth.html index baea08c4bd5..8b8b46ffa1e 100644 --- a/docs/manual/howto/auth.html +++ b/docs/manual/howto/auth.html @@ -14,26 +14,26 @@ vlink="#000080" alink="#FF0000"> -

Authentication

+

Authentication

@@ -81,7 +81,7 @@

This article covers the "standard" way of protecting parts of your web site that most of you are going to use.

-

The +

The prerequisites

The directives discussed in this article will need to go @@ -112,8 +112,8 @@ kept. This should not be terribly difficult, and I'll try to make this clear when we come to that point.

-

Getting it working

+

Getting it working

Here's the basics of password protecting a directory on your server.

@@ -221,8 +221,8 @@ server. In the next section, we discuss various ways to use the require directive.

-

Letting more than one +

Letting more than one person in

The directives above only let one person (specifically @@ -287,7 +287,7 @@ files, and remember to reference th right one in the AuthUserFile directive.

-

Possible +

Possible problems

Because of the way that Basic authentication is specified, @@ -308,8 +308,8 @@ get above a few hundred entries, and may wish to consider a different authentication method at that time.

-

What other neat stuff can +

What other neat stuff can I do?

Authentication by username and password is only part of the @@ -319,10 +319,9 @@

The allow and deny directives let you allow and deny access based on the host name, or host - address, of the machine requesting a document. The directive - goes hand-in-hand with these is the order - directive, which tells Apache in which order to apply the - filters.

+ address, of the machine requesting a document. The + order directive goes hand-in-hand with these two, + and tells Apache in which order to apply the filters.

The usage of these directives is:

@@ -331,7 +330,8 @@
 
     
where address is an IP address (or a partial IP
     address) or a fully qualified domain name (or a partial domain
-    name).

+    name); you may provide multiple addresses or domain names, if
+    desired.

 
     
For example, if you have someone spamming your message
     board, and you want to keep them out, you could do the
@@ -341,7 +341,7 @@

Visitors coming from that address will not be able to see - the content behind this directive. If, instead, you have a + the content covered by this directive. If, instead, you have a machine name, rather than an IP address, you can use that.

         deny from host.example.com
@@ -351,7 +351,7 @@
     you can specify just part of an address or domain name:

 
         deny from 192.101.205
-        deny from cyberthugs.com
+        deny from cyberthugs.com moreidiots.com
         deny from ke
 

 
@@ -370,7 +370,7 @@
     addition to letting everyone in. What you want is to let
     only those folks in.

 
-    
More
+    
More
     information

 
     
You should also read the documentation for 
     
 
-    
Authentication

+    
Authentication

      
      
 
     
     
     

@@ -81,7 +81,7 @@
     
This article covers the "standard" way of protecting parts
     of your web site that most of you are going to use.

 
-    
The
+    
The
     prerequisites

 
     
The directives discussed in this article will need to go
@@ -112,8 +112,8 @@
     kept. This should not be terribly difficult, and I'll try to
     make this clear when we come to that point.

 
-    
Getting it working

+    
Getting it working

 
     
Here's the basics of password protecting a directory on your
     server.

@@ -221,8 +221,8 @@
     server. In the next section, we discuss various ways to use the
     require directive.

 
-    
Letting more than one
+    
Letting more than one
     person in

 
     
The directives above only let one person (specifically
@@ -287,7 +287,7 @@
     files, and remember to reference th right one in the
     AuthUserFile directive.

 
-    
Possible
+    
Possible
     problems

 
     
Because of the way that Basic authentication is specified,
@@ -308,8 +308,8 @@
     get above a few hundred entries, and may wish to consider a
     different authentication method at that time.

 
-    
What other neat stuff can
+    
What other neat stuff can
     I do?

 
     
Authentication by username and password is only part of the
@@ -319,10 +319,9 @@
 
     
The allow and deny directives let
     you allow and deny access based on the host name, or host
-    address, of the machine requesting a document. The directive
-    goes hand-in-hand with these is the order
-    directive, which tells Apache in which order to apply the
-    filters.

+    address, of the machine requesting a document. The
+    order directive goes hand-in-hand with these two,
+    and tells Apache in which order to apply the filters.

 
     
The usage of these directives is:

 
@@ -331,7 +330,8 @@
 
     
where address is an IP address (or a partial IP
     address) or a fully qualified domain name (or a partial domain
-    name).

+    name); you may provide multiple addresses or domain names, if
+    desired.

 
     
For example, if you have someone spamming your message
     board, and you want to keep them out, you could do the
@@ -341,7 +341,7 @@
 

 
     
Visitors coming from that address will not be able to see
-    the content behind this directive. If, instead, you have a
+    the content covered by this directive. If, instead, you have a
     machine name, rather than an IP address, you can use that.

 
         deny from host.example.com
@@ -351,7 +351,7 @@
     you can specify just part of an address or domain name:

 
         deny from 192.101.205
-        deny from cyberthugs.com
+        deny from cyberthugs.com moreidiots.com
         deny from ke
 

 
@@ -370,7 +370,7 @@
     addition to letting everyone in. What you want is to let
     only those folks in.

 
-    
More
+    
More
     information

 
     
You should also read the documentation for