From: Daniel Gruno The usage of these directives is:
- Require host address
- Require ip ip.address
+Require host address
+Require ip ip.address
@@ -91,25 +91,23 @@
board, and you want to keep them out, you could do the
following:
- Require not ip 10.252.46.165
-
Require not ip 10.252.46.165+
Visitors coming from that address will not be able to see the content covered by this directive. If, instead, you have a machine name, rather than an IP address, you can use that.
-
- Require not host host.example.com
-
Require not host host.example.com+
And, if you'd like to block access from an entire domain, you can specify just part of an address or domain name:
- Require not ip 192.168.205 - Require not host phishers.example.com moreidiots.example - Require not gov +Require not ip 192.168.205 +Require not host phishers.example.com moreidiots.example +Require not gov@@ -127,9 +125,9 @@ following:
- <If "%{HTTP_USER_AGENT} = 'BadBot'"> - Require All Denied - </If> +<If "%{HTTP_USER_AGENT} = 'BadBot'"> + Require All Denied +</If>@@ -155,10 +153,10 @@ and 6am, you can do this using
mod_rewrite
.
- RewriteEngine On - RewriteCond %{TIME_HOUR} >20 [OR] - RewriteCond %{TIME_HOUR} <07 - RewriteRule ^/fridge - [F] +RewriteEngine On +RewriteCond %{TIME_HOUR} >20 [OR] +RewriteCond %{TIME_HOUR} <07 +RewriteRule ^/fridge - [F]diff --git a/docs/manual/howto/access.xml b/docs/manual/howto/access.xml index 62ffd60075..a24220af1b 100644 --- a/docs/manual/howto/access.xml +++ b/docs/manual/howto/access.xml @@ -68,8 +68,8 @@
The usage of these directives is:
In the first form, address is a fully qualified @@ -89,25 +89,21 @@ board, and you want to keep them out, you could do the following:
-Visitors coming from that address will not be able to see the content covered by this directive. If, instead, you have a machine name, rather than an IP address, you can use that.
-And, if you'd like to block access from an entire domain, you can specify just part of an address or domain name:
Use of the
This will return a 403 Forbidden response for any request after 8pm diff --git a/docs/manual/howto/auth.html.en b/docs/manual/howto/auth.html.en index 21aa5daea4..ea9344a2f5 100644 --- a/docs/manual/howto/auth.html.en +++ b/docs/manual/howto/auth.html.en @@ -142,9 +142,7 @@ module from each group.
anAllowOverride
directive like the
following:
- - AllowOverride AuthConfig -+
AllowOverride AuthConfig
Or, if you are just going to put the directives directly in @@ -218,12 +216,12 @@ module from each group.
/usr/local/apache/htdocs/secret> section.- AuthType Basic - AuthName "Restricted Files" - # (Following line optional) - AuthBasicProvider file - AuthUserFile /usr/local/apache/passwd/passwords - Require user rbowen +AuthType Basic +AuthName "Restricted Files" +# (Following line optional) +AuthBasicProvider file +AuthUserFile /usr/local/apache/passwd/passwords +Require user rbowen@@ -316,13 +314,13 @@ person in look like the following:
- AuthType Basic - AuthName "By Invitation Only" - # Optional line: - AuthBasicProvider file - AuthUserFile /usr/local/apache/passwd/passwords - AuthGroupFile /usr/local/apache/passwd/groups - Require group GroupName +AuthType Basic +AuthName "By Invitation Only" +# Optional line: +AuthBasicProvider file +AuthUserFile /usr/local/apache/passwd/passwords +AuthGroupFile /usr/local/apache/passwd/groups +Require group GroupName@@ -334,9 +332,8 @@ person in specific. Rather than creating a group file, you can just use the following directive: -
- Require valid-user
-
Require valid-user+
Using that rather than the Require user rbowen
line will allow anyone in that is listed in the password file,
@@ -383,13 +380,13 @@ person in
To select a dbd file rather than a text file, for example:
- <Directory /www/docs/private> - AuthName "Private" - AuthType Basic - AuthBasicProvider dbm - AuthDBMUserFile /www/passwords/passwd.dbm - Require valid-user - </Directory> +<Directory /www/docs/private> + AuthName "Private" + AuthType Basic + AuthBasicProvider dbm + AuthDBMUserFile /www/passwords/passwd.dbm + Require valid-user +</Directory>@@ -407,14 +404,14 @@ person in file and LDAP based authentication providers are being used.
- <Directory /www/docs/private> - AuthName "Private" - AuthType Basic - AuthBasicProvider file ldap - AuthUserFile /usr/local/apache/passwd/passwords - AuthLDAPURL ldap://ldaphost/o=yourorg - Require valid-user - </Directory> +<Directory /www/docs/private> + AuthName "Private" + AuthType Basic + AuthBasicProvider file ldap + AuthUserFile /usr/local/apache/passwd/passwords + AuthLDAPURL ldap://ldaphost/o=yourorg + Require valid-user +</Directory>@@ -432,16 +429,16 @@ person in authorization as well as LDAP group authorization is being used.
- <Directory /www/docs/private> - AuthName "Private" - AuthType Basic - AuthBasicProvider file - AuthUserFile /usr/local/apache/passwd/passwords - AuthLDAPURL ldap://ldaphost/o=yourorg - AuthGroupFile /usr/local/apache/passwd/groups - Require group GroupName - Require ldap-group cn=mygroup,o=yourorg - </Directory> +<Directory /www/docs/private> + AuthName "Private" + AuthType Basic + AuthBasicProvider file + AuthUserFile /usr/local/apache/passwd/passwords + AuthLDAPURL ldap://ldaphost/o=yourorg + AuthGroupFile /usr/local/apache/passwd/groups + Require group GroupName + Require ldap-group cn=mygroup,o=yourorg +</Directory>@@ -521,17 +518,13 @@ person in that will be called during the authorization stage of the request processing. For example: -
- Require ip address -+
Require ip address
where address is an IP address (or a partial IP address) or:
-- Require host domain_name -+
Require host domain_name
where domain_name is a fully qualified domain name @@ -543,10 +536,10 @@ person in following:
- <RequireAll> - Require all granted - Require not ip 10.252.46.165 - </RequireAll> +<RequireAll> + Require all granted + Require not ip 10.252.46.165 +</RequireAll>@@ -555,10 +548,10 @@ person in machine name, rather than an IP address, you can use that.
- <RequireAll> - Require all granted - Require not host host.example.com - </RequireAll> +<RequireAll> + Require all granted + Require not host host.example.com +</RequireAll>@@ -566,14 +559,14 @@ person in you can specify just part of an address or domain name:
- <RequireAll> +<RequireAll> Require all granted <RequireNone> - Require ip 192.168.205 - Require host phishers.example.com moreidiots.example - Require host ke + Require ip 192.168.205 + Require host phishers.example.com moreidiots.example + Require host ke </RequireNone> - </RequireAll> +</RequireAll>diff --git a/docs/manual/howto/auth.xml b/docs/manual/howto/auth.xml index 01e139818c..d5c5e1134b 100644 --- a/docs/manual/howto/auth.xml +++ b/docs/manual/howto/auth.xml @@ -127,9 +127,7 @@ module from each group. an
Or, if you are just going to put the directives directly in your main server configuration file, you will of course need to @@ -202,12 +200,12 @@ module from each group.
/usr/local/apache/htdocs/secret> section.Let's examine each of those directives individually. The
Now, anyone that is listed in the group GroupName
,
@@ -323,9 +321,7 @@ person in
specific. Rather than creating a group file, you can just use
the following directive:
Using that rather than the Require user rbowen
line will allow anyone in that is listed in the password file,
@@ -373,13 +369,13 @@ person in
To select a dbd file rather than a text file, for example:
Other options are available. Consult the @@ -396,14 +392,14 @@ person in file and LDAP based authentication providers are being used.
In this example the file provider will attempt to authenticate @@ -420,16 +416,16 @@ person in authorization as well as LDAP group authorization is being used.
To take authorization a little further, authorization container @@ -508,16 +504,12 @@ person in that will be called during the authorization stage of the request processing. For example:
-where address is an IP address (or a partial IP address) or:
-where domain_name is a fully qualified domain name (or a partial domain name); you may provide multiple addresses or @@ -528,10 +520,10 @@ person in following:
Visitors coming from that address will not be able to see @@ -539,24 +531,24 @@ person in machine name, rather than an IP address, you can use that.
And, if you'd like to block access from an entire domain, you can specify just part of an address or domain name:
The above example uses the