From 0dec36fd786d7c02ae019b0241e9179a3b9a74b0 Mon Sep 17 00:00:00 2001 From: Mike Rumph Date: Wed, 4 Jun 2014 00:54:08 +0000 Subject: [PATCH] Fix spelling and grammar errors. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1599844 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/howto/auth.html.en | 22 +++++++++++----------- docs/manual/howto/auth.xml | 20 ++++++++++---------- 2 files changed, 21 insertions(+), 21 deletions(-) diff --git a/docs/manual/howto/auth.html.en b/docs/manual/howto/auth.html.en index d9ea1fdf8a..29c383687b 100644 --- a/docs/manual/howto/auth.html.en +++ b/docs/manual/howto/auth.html.en @@ -46,7 +46,7 @@ person in
  • Alternate password storage
  • Using multiple providers
  • Beyond just authorization
    • -
  • Authentication Cacheing
    • +
  • Authentication Caching
  • More information
    • top
    @@ -94,7 +94,7 @@ module from each group.

    In addition to these modules, there are also mod_authn_core and - mod_authz_core. These module implement core + mod_authz_core. These modules implement core directives that are core to all auth modules.

    The module mod_authnz_ldap is both an @@ -174,7 +174,7 @@ module from each group.

    This file should be placed somewhere not accessible from the web. This is so that folks cannot download the password file. For example, if your - documents are served out of /usr/local/apache/htdocs you + documents are served out of /usr/local/apache/htdocs, you might want to put the password file(s) in /usr/local/apache/passwd.

    @@ -433,20 +433,20 @@ Require group GroupName and <RequireAny> allow logic to be applied so that the order in which authorization - is handled can be completely controled through the configuration. + is handled can be completely controlled through the configuration. See Authorization - Containers for an example of they may be applied.

    + Containers for an example of how they may be applied.

    top

    Beyond just authorization

    -

    The way that authorization can be apply is now much more flexible +

    The way that authorization can be applied is now much more flexible than just a single check against a single data store. Ordering, logic and choosing how authorization will be done is now possible.

    Applying logic and ordering

    -

    Controling how and in what order authorization will be applied +

    Controlling how and in what order authorization will be applied has been a bit of a mystery in the past. In Apache 2.2 a provider-based authentication mechanism was introduced to decouple the actual authentication process from authorization and supporting functionality. @@ -491,7 +491,7 @@ Require group GroupName

    The authorization providers all, env, host and ip let you - allow or deny access based other host based criteria such as + allow or deny access based on other host based criteria such as host name or ip address of the machine requesting a document.

    @@ -554,7 +554,7 @@ Require group GroupName

    Access Control backwards compatibility

    One of the side effects of adopting a provider based mechanism for - authentication is that the need for the previous access control directives + authentication is that the previous access control directives Order, Allow, Deny and @@ -565,11 +565,11 @@ Require group GroupName

    top
    -

    Authentication Cacheing

    +

    Authentication Caching

    There may be times when authentication puts an unacceptable load on a provider or on your network. This is most likely to affect users of mod_authn_dbd (or third-party/custom providers). - To deal with this, HTTPD 2.3/2.4 introduces a new cacheing provider + To deal with this, HTTPD 2.3/2.4 introduces a new caching provider mod_authn_socache to cache credentials and reduce the load on the origin provider(s).

    This may offer a substantial performance boost to some users.

    diff --git a/docs/manual/howto/auth.xml b/docs/manual/howto/auth.xml index d83fbaac93..d6d80f4af4 100644 --- a/docs/manual/howto/auth.xml +++ b/docs/manual/howto/auth.xml @@ -78,7 +78,7 @@ module from each group.

    In addition to these modules, there are also mod_authn_core and - mod_authz_core. These module implement core + mod_authz_core. These modules implement core directives that are core to all auth modules.

    The module mod_authnz_ldap is both an @@ -158,7 +158,7 @@ module from each group.

    This file should be placed somewhere not accessible from the web. This is so that folks cannot download the password file. For example, if your - documents are served out of /usr/local/apache/htdocs you + documents are served out of /usr/local/apache/htdocs, you might want to put the password file(s) in /usr/local/apache/passwd.

    @@ -430,20 +430,20 @@ Require group GroupName and RequireAny allow logic to be applied so that the order in which authorization - is handled can be completely controled through the configuration. + is handled can be completely controlled through the configuration. See Authorization - Containers for an example of they may be applied.

    + Containers for an example of how they may be applied.

    Beyond just authorization -

    The way that authorization can be apply is now much more flexible +

    The way that authorization can be applied is now much more flexible than just a single check against a single data store. Ordering, logic and choosing how authorization will be done is now possible.

    Applying logic and ordering -

    Controling how and in what order authorization will be applied +

    Controlling how and in what order authorization will be applied has been a bit of a mystery in the past. In Apache 2.2 a provider-based authentication mechanism was introduced to decouple the actual authentication process from authorization and supporting functionality. @@ -488,7 +488,7 @@ Require group GroupName

    The authorization providers all, env, host and ip let you - allow or deny access based other host based criteria such as + allow or deny access based on other host based criteria such as host name or ip address of the machine requesting a document.

    @@ -553,7 +553,7 @@ Require group GroupName
    Access Control backwards compatibility

    One of the side effects of adopting a provider based mechanism for - authentication is that the need for the previous access control directives + authentication is that the previous access control directives Order, Allow, Deny and @@ -564,11 +564,11 @@ Require group GroupName

    -
    Authentication Cacheing +
    Authentication Caching

    There may be times when authentication puts an unacceptable load on a provider or on your network. This is most likely to affect users of mod_authn_dbd (or third-party/custom providers). - To deal with this, HTTPD 2.3/2.4 introduces a new cacheing provider + To deal with this, HTTPD 2.3/2.4 introduces a new caching provider mod_authn_socache to cache credentials and reduce the load on the origin provider(s).

    This may offer a substantial performance boost to some users.

    -- 2.40.0