From: Rich Bowen Date: Wed, 16 Feb 2011 12:06:43 +0000 (+0000) Subject: Whitespace and small phrasing changes. X-Git-Tag: 2.3.11~31 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=100521645e686c7c3d634d280da6b0cb3a62bac7;p=thirdparty%2Fapache%2Fhttpd.git Whitespace and small phrasing changes. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1071215 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/howto/access.html.en b/docs/manual/howto/access.html.en index 2a01f71fbf5..d0e3f0b446d 100644 --- a/docs/manual/howto/access.html.en +++ b/docs/manual/howto/access.html.en @@ -26,7 +26,7 @@
@@ -34,10 +34,10 @@

Related Modules and Directives

-

Access control can be done by several different modules. The most -important of these are mod_authz_core and -mod_authz_host. Also discussed in this document -is access control using mod_rewrite.

+

Access control can be done by several different modules. The most + important of these are mod_authz_core and + mod_authz_host. Also discussed in this document + is access control using mod_rewrite.

top
@@ -78,7 +78,12 @@ is access control using m partial IP address, a network/netmask pair, or a network/nnn CIDR specification. Either IPv4 or IPv6 addresses may be used.

-

For example, if you have someone spamming your message +

See the + mod_authz_host documentation for further examples of this + syntax.

+ +

You can insert not to negate a particular requirement. + For example, if you have someone spamming your message board, and you want to keep them out, you could do the following:

@@ -108,7 +113,7 @@ is access control using m
top
-

Access control by environment variable

+

Access control by arbitrary variables

Using the <If>, you can allow or deny access based on arbitrary environment @@ -138,29 +143,29 @@ is access control using m

Access control with mod_rewrite

-

The [F] RewriteRule flag causes a 403 Forbidden -response to be sent. Using this, you can deny access to a resource based -on arbitrary criteria.

- -

For example, if you wish to block access to a resource between 8pm -and 6am, you can do this using mod_rewrite.

- -

-RewriteEngine On
-RewriteCond %{TIME_HOUR} >20 [OR]
-RewriteCond %{TIME_HOUR} <07
-RewriteRule ^/fridge - [F] -

- -

This will return a 403 Forbidden response for any request after 8pm -or before 7am. This technique can be used for any criteria that you wish -to check. You can also redirect, or otherwise rewrite these requests, if -that approach is preferred.

- -

The <If> directive, -added in 2.4, replaces many things that mod_rewrite has -traditionally been used to do, and you should probably look there first -before resorting to mod_rewrite.

+

The [F] RewriteRule flag causes a 403 Forbidden + response to be sent. Using this, you can deny access to a resource based + on arbitrary criteria.

+ +

For example, if you wish to block access to a resource between 8pm + and 6am, you can do this using mod_rewrite.

+ +

+ RewriteEngine On
+ RewriteCond %{TIME_HOUR} >20 [OR]
+ RewriteCond %{TIME_HOUR} <07
+ RewriteRule ^/fridge - [F] +

+ +

This will return a 403 Forbidden response for any request after 8pm + or before 7am. This technique can be used for any criteria that you wish + to check. You can also redirect, or otherwise rewrite these requests, if + that approach is preferred.

+ +

The <If> directive, + added in 2.4, replaces many things that mod_rewrite has + traditionally been used to do, and you should probably look there first + before resorting to mod_rewrite.

top
diff --git a/docs/manual/howto/access.xml b/docs/manual/howto/access.xml index 13cbd9074a8..084b968e23a 100644 --- a/docs/manual/howto/access.xml +++ b/docs/manual/howto/access.xml @@ -33,10 +33,10 @@ @@ -80,7 +80,12 @@ is access control using mod_rewrite.

partial IP address, a network/netmask pair, or a network/nnn CIDR specification. Either IPv4 or IPv6 addresses may be used.

-

For example, if you have someone spamming your message +

See the + mod_authz_host documentation for further examples of this + syntax.

+ +

You can insert not to negate a particular requirement. + For example, if you have someone spamming your message board, and you want to keep them out, you could do the following:

@@ -113,7 +118,7 @@ is access control using mod_rewrite.

-
Access control by environment variable +
Access control by arbitrary variables

Using the If, you can allow or deny access based on arbitrary environment @@ -143,30 +148,30 @@ is access control using mod_rewrite.

Access control with mod_rewrite -

The [F] RewriteRule flag causes a 403 Forbidden -response to be sent. Using this, you can deny access to a resource based -on arbitrary criteria.

- -

For example, if you wish to block access to a resource between 8pm -and 6am, you can do this using mod_rewrite.

- - -RewriteEngine On
-RewriteCond %{TIME_HOUR} >20 [OR]
-RewriteCond %{TIME_HOUR} <07
-RewriteRule ^/fridge - [F] - - -

This will return a 403 Forbidden response for any request after 8pm -or before 7am. This technique can be used for any criteria that you wish -to check. You can also redirect, or otherwise rewrite these requests, if -that approach is preferred.

- -

The If directive, -added in 2.4, replaces many things that mod_rewrite has -traditionally been used to do, and you should probably look there first -before resorting to mod_rewrite.

+

The [F] RewriteRule flag causes a 403 Forbidden + response to be sent. Using this, you can deny access to a resource based + on arbitrary criteria.

+ +

For example, if you wish to block access to a resource between 8pm + and 6am, you can do this using mod_rewrite.

+ + + RewriteEngine On
+ RewriteCond %{TIME_HOUR} >20 [OR]
+ RewriteCond %{TIME_HOUR} <07
+ RewriteRule ^/fridge - [F] + + +

This will return a 403 Forbidden response for any request after 8pm + or before 7am. This technique can be used for any criteria that you wish + to check. You can also redirect, or otherwise rewrite these requests, if + that approach is preferred.

+ +

The If directive, + added in 2.4, replaces many things that mod_rewrite has + traditionally been used to do, and you should probably look there first + before resorting to mod_rewrite.