From: Jim Jagielski Date: Mon, 19 Aug 2019 16:17:13 +0000 (+0000) Subject: xforms X-Git-Tag: 2.4.42~284 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bd889e4ebc22080d89c04f9f2f8430ed72eee2cb;p=thirdparty%2Fapache%2Fhttpd.git xforms git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1865475 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_authn_socache.html.en b/docs/manual/mod/mod_authn_socache.html.en index 051bb6ac460..7b5b5dd371d 100644 --- a/docs/manual/mod/mod_authn_socache.html.en +++ b/docs/manual/mod/mod_authn_socache.html.en @@ -42,9 +42,9 @@ the load on backends
Support Apache!

Topics

Directives

top
-

Authentication Cacheing

+

Authentication Caching

Some users of more heavyweight authentication such as SQL database lookups (mod_authn_dbd) have reported it putting an unacceptable load on their authentication provider. A typical case @@ -66,7 +66,7 @@ the load on backends (images, scripts, stylesheets, media, etc), and a request to the page generates hundreds of effectively-immediate requests for authenticated additional contents.

-

mod_authn_socache provides a solution to this problem by +

mod_authn_socache provides a solution to this problem by maintaining a cache of authentication credentials.

top
@@ -76,16 +76,16 @@ the load on backends network. Authentication by file (mod_authn_file) or dbm (mod_authn_dbm) are unlikely to benefit, as these are fast and lightweight in their own right (though in some - cases, such as a network-mounted file, cacheing may be worthwhile). + cases, such as a network-mounted file, caching may be worthwhile). Other providers such as SQL or LDAP based authentication are more likely to benefit, particularly where there is an observed performance issue. Amongst the standard modules, mod_authnz_ldap manages its own cache, so only mod_authn_dbd will usually benefit from this cache.

The basic rules to cache for a provider are:

-
  1. Include the provider you're cacheing for in an - AuthnCacheProvideFor directive.
  2. +
    1. Include the provider you're caching for in an + AuthnCacheProvideFor directive.
    2. List socache ahead of the provider you're - cacheing for in your AuthBasicProvider or AuthDigestProvider directive.
    3. + caching for in your AuthBasicProvider or AuthDigestProvider directive.

    A simple usage example to accelerate mod_authn_dbd using dbm as a cache engine:

    @@ -104,19 +104,19 @@ AuthnCacheSOCache dbm
top
-

Cacheing with custom modules

+

Caching with custom modules

Module developers should note that their modules must be enabled - for cacheing with mod_authn_socache. A single optional API function + for caching with mod_authn_socache. A single optional API function ap_authn_cache_store is provided to cache credentials a provider has just looked up or generated. Usage examples are - available in r957072, in which three authn providers are enabled for cacheing.

+ available in r957072, in which three authn providers are enabled for caching.

top

AuthnCacheContext Directive

- - + + @@ -125,10 +125,10 @@ AuthnCacheSOCache dbm username (and realm in the case of Digest Authentication) in constructing a cache key. This serves to disambiguate identical usernames serving different authentication areas on the server.

-

Two special values for this are directory, which uses - the directory context of the request as a string, and server +

Two special values for this are directory, which uses + the directory context of the request as a string, and server which uses the virtual host name.

-

The default is directory, which is also the most +

The default is directory, which is also the most conservative setting. This is likely to be less than optimal, as it (for example) causes $app-base, $app-base/images, $app-base/scripts and $app-base/media each to @@ -151,7 +151,7 @@ AuthnCacheSOCache dbm

Description:Specify a context string for use in the cache key
Syntax:AuthnCacheContext directory|server|custom-string
Default:directory
Syntax:AuthnCacheContext directory|server|custom-string
Default:AuthnCacheContext directory
Context:directory
Status:Base
Module:mod_authn_socache
Module:mod_authn_socache

This directive is not normally necessary: it is implied if - authentication cacheing is enabled anywhere in httpd.conf. + authentication caching is enabled anywhere in httpd.conf. However, if it is not enabled anywhere in httpd.conf it will by default not be initialised, and is therefore not available in a .htaccess context. This directive @@ -171,7 +171,7 @@ AuthnCacheSOCache dbm

This directive specifies an authentication provider or providers to cache for. Credentials found by a provider not listed in an - AuthnCacheProvideFor directive will not be cached.

+ AuthnCacheProvideFor directive will not be cached.

For example, to cache credentials found by mod_authn_dbd or by a custom provider myprovider, but leave those looked @@ -204,14 +204,14 @@ Apache HTTP Server 2.4.7 and later - +
Description:Set a timeout for cache entries
Syntax:AuthnCacheTimeout timeout (seconds)
Default:300 (5 minutes)
Default:AuthnCacheTimeout 300 (5 minutes)
Context:directory, .htaccess
Override:AuthConfig
Status:Base
Module:mod_authn_socache
-

Cacheing authentication data can be a security issue, though short-term - cacheing is unlikely to be a problem. Typically a good solution is to +

Caching authentication data can be a security issue, though short-term + caching is unlikely to be a problem. Typically a good solution is to cache credentials for as long as it takes to relieve the load on a backend, but no longer, though if changes to your users and passwords are infrequent then a longer timeout may suit you. The default 300 diff --git a/docs/manual/mod/mod_authn_socache.html.fr.utf8 b/docs/manual/mod/mod_authn_socache.html.fr.utf8 index 37922ded2d6..9002f9278bf 100644 --- a/docs/manual/mod/mod_authn_socache.html.fr.utf8 +++ b/docs/manual/mod/mod_authn_socache.html.fr.utf8 @@ -29,6 +29,8 @@

Langues Disponibles:  en  |  fr 

+
Cette traduction peut être périmée. Vérifiez la version + anglaise pour les changements récents.
diff --git a/docs/manual/mod/mod_authn_socache.xml.fr b/docs/manual/mod/mod_authn_socache.xml.fr index 1c9d4cea227..8d92c36acba 100644 --- a/docs/manual/mod/mod_authn_socache.xml.fr +++ b/docs/manual/mod/mod_authn_socache.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/mod/mod_authn_socache.xml.meta b/docs/manual/mod/mod_authn_socache.xml.meta index cdd1381068f..82079557048 100644 --- a/docs/manual/mod/mod_authn_socache.xml.meta +++ b/docs/manual/mod/mod_authn_socache.xml.meta @@ -8,6 +8,6 @@ en - fr + fr diff --git a/docs/manual/mod/mod_deflate.html.en b/docs/manual/mod/mod_deflate.html.en index 35126e1d4b7..9e372c42eb9 100644 --- a/docs/manual/mod/mod_deflate.html.en +++ b/docs/manual/mod/mod_deflate.html.en @@ -71,7 +71,7 @@ content

Supported Encodings

The gzip encoding is the only one supported to ensure complete compatibility with old browser implementations. The deflate encoding is not supported, - please check the zlib's documentation + please check the zlib's documentation for a complete explanation.

top
@@ -205,7 +205,7 @@ content

Since mod_deflate re-compresses content each time a request is made, some performance benefit can be derived by - pre-compressing the content and telling mod_deflate to serve them + pre-compressing the content and telling mod_deflate to serve them without re-compressing them. This may be accomplished using a configuration like the following:

@@ -214,8 +214,7 @@ content # and the client accepts gzip. RewriteCond "%{HTTP:Accept-encoding}" "gzip" RewriteCond "%{REQUEST_FILENAME}\.gz" -s - RewriteRule "^(.*)\.(css|js)" "$1\.$2\.gz" [QSA] - + RewriteRule "^(.*)\.(css|js)" "$1\.$2\.gz" [QSA] # Serve correct content types, and prevent mod_deflate double gzip. RewriteRule "\.css\.gz$" "-" [T=text/css,E=no-gzip:1] diff --git a/docs/manual/mod/mod_deflate.html.fr.utf8 b/docs/manual/mod/mod_deflate.html.fr.utf8 index ab4071aa296..5b42b396a0c 100644 --- a/docs/manual/mod/mod_deflate.html.fr.utf8 +++ b/docs/manual/mod/mod_deflate.html.fr.utf8 @@ -31,6 +31,8 @@  ja  |  ko 

+
Cette traduction peut être périmée. Vérifiez la version + anglaise pour les changements récents.
Description:Gère un cache des données d'authentification pour diminuer la charge des serveurs d'arrière-plan
Statut:Base
diff --git a/docs/manual/mod/mod_deflate.xml.fr b/docs/manual/mod/mod_deflate.xml.fr index 825774d0aaa..116d31e7d3e 100644 --- a/docs/manual/mod/mod_deflate.xml.fr +++ b/docs/manual/mod/mod_deflate.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/mod/mod_deflate.xml.ja b/docs/manual/mod/mod_deflate.xml.ja index 82fd12b31e9..a00d83fd866 100644 --- a/docs/manual/mod/mod_deflate.xml.ja +++ b/docs/manual/mod/mod_deflate.xml.ja @@ -1,7 +1,7 @@ - + +
Description:Comprime le contenu avant de le servir au client
Statut:Extension