From 57ef10245b3cf962dcbe40d205d94c241bed7f0e Mon Sep 17 00:00:00 2001 From: Ken Coar Date: Wed, 15 Apr 2015 17:46:53 +0000 Subject: [PATCH] Enclose parameters in quotation marks for <{Files,Directory,Location}{,Match}> containers. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1673892 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/developer/lua.html.en | 4 +- docs/manual/developer/lua.xml | 4 +- docs/manual/env.html.en | 2 +- docs/manual/env.xml | 2 +- docs/manual/expr.html.en | 2 +- docs/manual/expr.xml | 2 +- docs/manual/handler.html.en | 2 +- docs/manual/handler.xml | 2 +- docs/manual/howto/cgi.html.en | 6 +- docs/manual/howto/cgi.xml | 6 +- docs/manual/howto/public_html.html.en | 2 +- docs/manual/howto/public_html.xml | 2 +- docs/manual/misc/perf-scaling.html.en | 5 +- docs/manual/misc/perf-scaling.xml | 5 +- docs/manual/misc/perf-tuning.html.en | 10 +- docs/manual/misc/perf-tuning.xml | 10 +- docs/manual/misc/security_tips.html.en | 12 +- docs/manual/misc/security_tips.xml | 12 +- docs/manual/mod/core.html.de | 2 +- docs/manual/mod/core.html.en | 42 +- docs/manual/mod/core.html.es | 2 +- docs/manual/mod/core.html.fr | 2 +- docs/manual/mod/core.html.ja.utf8 | 2 +- docs/manual/mod/core.html.tr.utf8 | 2 +- docs/manual/mod/core.xml | 40 +- docs/manual/mod/event.html.en | 104 +- docs/manual/mod/event.html.fr | 128 +- docs/manual/mod/mod_access_compat.html.en | 10 +- docs/manual/mod/mod_access_compat.html.fr | 2 +- .../manual/mod/mod_access_compat.html.ja.utf8 | 2 +- docs/manual/mod/mod_access_compat.xml | 8 +- docs/manual/mod/mod_actions.html.de | 2 +- docs/manual/mod/mod_actions.html.en | 4 +- docs/manual/mod/mod_actions.html.fr | 2 +- docs/manual/mod/mod_actions.html.ja.utf8 | 2 +- docs/manual/mod/mod_actions.html.ko.euc-kr | 2 +- docs/manual/mod/mod_actions.xml | 2 +- docs/manual/mod/mod_alias.html.en | 102 +- docs/manual/mod/mod_alias.html.fr | 90 +- docs/manual/mod/mod_alias.html.ja.utf8 | 66 +- docs/manual/mod/mod_alias.html.ko.euc-kr | 68 +- docs/manual/mod/mod_alias.html.tr.utf8 | 78 +- docs/manual/mod/mod_alias.xml | 20 +- docs/manual/mod/mod_allowhandlers.html.en | 6 +- docs/manual/mod/mod_allowhandlers.xml | 4 +- docs/manual/mod/mod_allowmethods.html.en | 6 +- docs/manual/mod/mod_allowmethods.html.fr | 2 +- docs/manual/mod/mod_allowmethods.xml | 4 +- docs/manual/mod/mod_asis.html.fr | 8 +- docs/manual/mod/mod_asis.html.ja.utf8 | 8 +- docs/manual/mod/mod_asis.html.ko.euc-kr | 8 +- docs/manual/mod/mod_auth_basic.html.en | 2 +- docs/manual/mod/mod_auth_basic.html.fr | 2 +- docs/manual/mod/mod_auth_basic.html.ja.utf8 | 2 +- docs/manual/mod/mod_auth_basic.html.ko.euc-kr | 2 +- docs/manual/mod/mod_auth_digest.html.en | 84 +- docs/manual/mod/mod_auth_digest.html.fr | 96 +- .../manual/mod/mod_auth_digest.html.ko.euc-kr | 150 +- docs/manual/mod/mod_auth_form.html.en | 712 ++++---- docs/manual/mod/mod_auth_form.html.fr | 602 +++---- docs/manual/mod/mod_auth_form.xml | 4 +- docs/manual/mod/mod_authn_anon.html.en | 86 +- docs/manual/mod/mod_authn_anon.html.fr | 100 +- docs/manual/mod/mod_authn_anon.html.ja.utf8 | 96 +- docs/manual/mod/mod_authn_anon.html.ko.euc-kr | 100 +- docs/manual/mod/mod_authn_core.html.en | 144 +- docs/manual/mod/mod_authn_core.html.fr | 168 +- docs/manual/mod/mod_authn_dbd.html.en | 150 +- docs/manual/mod/mod_authn_dbd.html.fr | 164 +- docs/manual/mod/mod_authn_dbd.xml | 2 +- docs/manual/mod/mod_authn_dbm.html.en | 2 +- docs/manual/mod/mod_authn_dbm.html.fr | 2 +- docs/manual/mod/mod_authn_dbm.html.ja.utf8 | 2 +- docs/manual/mod/mod_authn_dbm.html.ko.euc-kr | 2 +- docs/manual/mod/mod_authn_file.html.en | 2 +- docs/manual/mod/mod_authn_file.html.fr | 2 +- docs/manual/mod/mod_authn_file.html.ja.utf8 | 2 +- docs/manual/mod/mod_authn_file.html.ko.euc-kr | 2 +- docs/manual/mod/mod_authn_socache.html.en | 110 +- docs/manual/mod/mod_authn_socache.html.fr | 148 +- docs/manual/mod/mod_authn_socache.xml | 2 +- docs/manual/mod/mod_authnz_fcgi.html.en | 250 +-- docs/manual/mod/mod_authnz_fcgi.xml | 8 +- docs/manual/mod/mod_authnz_ldap.html.en | 1228 +++++++------- docs/manual/mod/mod_authnz_ldap.html.fr | 1426 ++++++++--------- docs/manual/mod/mod_authz_core.html.en | 408 ++--- docs/manual/mod/mod_authz_core.html.fr | 420 ++--- docs/manual/mod/mod_authz_dbd.html.en | 174 +- docs/manual/mod/mod_authz_dbd.html.fr | 202 +-- docs/manual/mod/mod_authz_dbd.xml | 6 +- docs/manual/mod/mod_authz_dbm.html.en | 98 +- docs/manual/mod/mod_authz_dbm.html.fr | 112 +- docs/manual/mod/mod_authz_dbm.html.ko.euc-kr | 2 +- docs/manual/mod/mod_authz_groupfile.html.en | 68 +- docs/manual/mod/mod_authz_groupfile.html.fr | 78 +- .../mod/mod_authz_groupfile.html.ja.utf8 | 2 +- .../mod/mod_authz_groupfile.html.ko.euc-kr | 2 +- docs/manual/mod/mod_authz_host.html.fr | 8 +- docs/manual/mod/mod_authz_owner.html.fr | 8 +- docs/manual/mod/mod_authz_owner.html.ja.utf8 | 8 +- .../manual/mod/mod_authz_owner.html.ko.euc-kr | 8 +- docs/manual/mod/mod_authz_user.html.fr | 8 +- docs/manual/mod/mod_autoindex.html.en | 210 +-- docs/manual/mod/mod_autoindex.html.fr | 230 +-- docs/manual/mod/mod_autoindex.html.ja.utf8 | 230 +-- docs/manual/mod/mod_autoindex.html.ko.euc-kr | 192 +-- docs/manual/mod/mod_autoindex.html.tr.utf8 | 194 +-- docs/manual/mod/mod_autoindex.xml | 6 +- docs/manual/mod/mod_autoindex.xml.fr | 2 +- docs/manual/mod/mod_autoindex.xml.ja | 2 +- docs/manual/mod/mod_autoindex.xml.ko | 2 +- docs/manual/mod/mod_autoindex.xml.meta | 2 +- docs/manual/mod/mod_autoindex.xml.tr | 2 +- docs/manual/mod/mod_buffer.html.en | 2 +- docs/manual/mod/mod_buffer.html.fr | 2 +- docs/manual/mod/mod_cache.html.en | 376 ++--- docs/manual/mod/mod_cache.html.fr | 442 ++--- docs/manual/mod/mod_cache.html.ja.utf8 | 100 +- docs/manual/mod/mod_cache.html.ko.euc-kr | 92 +- docs/manual/mod/mod_cache.xml | 6 +- docs/manual/mod/mod_cache_disk.html.en | 2 +- docs/manual/mod/mod_cache_disk.html.fr | 2 +- docs/manual/mod/mod_cache_disk.html.ja.utf8 | 2 +- docs/manual/mod/mod_cache_disk.html.ko.euc-kr | 2 +- docs/manual/mod/mod_cache_socache.html.en | 6 +- docs/manual/mod/mod_cache_socache.html.fr | 2 +- docs/manual/mod/mod_cache_socache.xml | 4 +- docs/manual/mod/mod_cern_meta.html.en | 2 +- docs/manual/mod/mod_cern_meta.html.fr | 2 +- docs/manual/mod/mod_cern_meta.html.ko.euc-kr | 2 +- docs/manual/mod/mod_cgi.html.en | 144 +- docs/manual/mod/mod_cgi.html.fr | 176 +- docs/manual/mod/mod_cgi.html.ja.utf8 | 162 +- docs/manual/mod/mod_cgi.html.ko.euc-kr | 150 +- docs/manual/mod/mod_cgid.html.en | 2 +- docs/manual/mod/mod_cgid.html.fr | 2 +- docs/manual/mod/mod_cgid.html.ja.utf8 | 2 +- docs/manual/mod/mod_cgid.html.ko.euc-kr | 2 +- docs/manual/mod/mod_charset_lite.html.en | 78 +- docs/manual/mod/mod_charset_lite.html.fr | 92 +- .../mod/mod_charset_lite.html.ko.euc-kr | 78 +- docs/manual/mod/mod_charset_lite.xml | 4 +- docs/manual/mod/mod_dav.html.en | 148 +- docs/manual/mod/mod_dav.html.fr | 178 +- docs/manual/mod/mod_dav.html.ja.utf8 | 174 +- docs/manual/mod/mod_dav.html.ko.euc-kr | 172 +- docs/manual/mod/mod_dav_fs.html.en | 2 +- docs/manual/mod/mod_dav_fs.html.fr | 2 +- docs/manual/mod/mod_dav_fs.html.ja.utf8 | 2 +- docs/manual/mod/mod_dav_fs.html.ko.euc-kr | 2 +- docs/manual/mod/mod_dav_lock.html.en | 2 +- docs/manual/mod/mod_dav_lock.html.fr | 2 +- docs/manual/mod/mod_dav_lock.html.ja.utf8 | 2 +- docs/manual/mod/mod_dbd.html.en | 228 +-- docs/manual/mod/mod_dbd.html.fr | 270 ++-- docs/manual/mod/mod_deflate.html.en | 332 ++-- docs/manual/mod/mod_deflate.html.fr | 296 ++-- docs/manual/mod/mod_deflate.html.ja.utf8 | 358 ++--- docs/manual/mod/mod_deflate.html.ko.euc-kr | 346 ++-- docs/manual/mod/mod_deflate.xml | 4 +- docs/manual/mod/mod_dialup.html.en | 6 +- docs/manual/mod/mod_dialup.html.fr | 2 +- docs/manual/mod/mod_dialup.xml | 4 +- docs/manual/mod/mod_dir.html.en | 14 +- docs/manual/mod/mod_dir.html.fr | 2 +- docs/manual/mod/mod_dir.html.ja.utf8 | 2 +- docs/manual/mod/mod_dir.html.ko.euc-kr | 2 +- docs/manual/mod/mod_dir.html.tr.utf8 | 2 +- docs/manual/mod/mod_dir.xml | 12 +- docs/manual/mod/mod_dumpio.html.en | 28 +- docs/manual/mod/mod_dumpio.html.fr | 38 +- docs/manual/mod/mod_dumpio.html.ja.utf8 | 30 +- docs/manual/mod/mod_echo.html.en | 2 +- docs/manual/mod/mod_echo.html.fr | 2 +- docs/manual/mod/mod_echo.html.ja.utf8 | 2 +- docs/manual/mod/mod_echo.html.ko.euc-kr | 2 +- docs/manual/mod/mod_env.html.en | 2 +- docs/manual/mod/mod_env.html.fr | 2 +- docs/manual/mod/mod_env.html.ja.utf8 | 2 +- docs/manual/mod/mod_env.html.ko.euc-kr | 2 +- docs/manual/mod/mod_env.html.tr.utf8 | 2 +- docs/manual/mod/mod_example_hooks.html.en | 42 +- docs/manual/mod/mod_example_hooks.html.fr | 54 +- .../mod/mod_example_hooks.html.ko.euc-kr | 48 +- docs/manual/mod/mod_example_hooks.xml | 2 +- docs/manual/mod/mod_expires.html.en | 114 +- docs/manual/mod/mod_expires.html.fr | 126 +- docs/manual/mod/mod_expires.html.ja.utf8 | 136 +- docs/manual/mod/mod_expires.html.ko.euc-kr | 134 +- docs/manual/mod/mod_ext_filter.html.en | 248 +-- docs/manual/mod/mod_ext_filter.html.fr | 278 ++-- docs/manual/mod/mod_ext_filter.html.ja.utf8 | 288 ++-- docs/manual/mod/mod_ext_filter.html.ko.euc-kr | 270 ++-- docs/manual/mod/mod_ext_filter.xml | 8 +- docs/manual/mod/mod_file_cache.html.en | 116 +- docs/manual/mod/mod_file_cache.html.fr | 142 +- docs/manual/mod/mod_file_cache.html.ko.euc-kr | 124 +- docs/manual/mod/mod_filter.html.en | 390 ++--- docs/manual/mod/mod_filter.xml | 4 +- docs/manual/mod/mod_firehose.html.en | 180 +-- docs/manual/mod/mod_headers.html.en | 304 ++-- docs/manual/mod/mod_headers.html.fr | 348 ++-- docs/manual/mod/mod_headers.html.ja.utf8 | 220 +-- docs/manual/mod/mod_headers.html.ko.euc-kr | 224 +-- docs/manual/mod/mod_heartbeat.html.en | 38 +- docs/manual/mod/mod_heartmonitor.html.en | 2 +- docs/manual/mod/mod_ident.html.en | 2 +- docs/manual/mod/mod_ident.html.fr | 2 +- docs/manual/mod/mod_ident.html.ja.utf8 | 2 +- docs/manual/mod/mod_ident.html.ko.euc-kr | 2 +- docs/manual/mod/mod_imagemap.html.en | 176 +- docs/manual/mod/mod_imagemap.html.ko.euc-kr | 178 +- docs/manual/mod/mod_include.html.en | 552 +++---- docs/manual/mod/mod_include.html.ja.utf8 | 454 +++--- docs/manual/mod/mod_info.html.en | 46 +- docs/manual/mod/mod_info.html.fr | 52 +- docs/manual/mod/mod_info.html.ja.utf8 | 60 +- docs/manual/mod/mod_info.html.ko.euc-kr | 58 +- docs/manual/mod/mod_info.xml | 6 +- docs/manual/mod/mod_isapi.html.en | 206 +-- docs/manual/mod/mod_isapi.html.ko.euc-kr | 214 +-- docs/manual/mod/mod_journald.html.en | 44 +- .../manual/mod/mod_lbmethod_heartbeat.html.en | 2 +- docs/manual/mod/mod_ldap.html.en | 678 ++++---- docs/manual/mod/mod_ldap.html.fr | 746 ++++----- docs/manual/mod/mod_ldap.xml | 12 +- docs/manual/mod/mod_log_config.html.en | 360 ++--- docs/manual/mod/mod_log_config.html.ja.utf8 | 370 ++--- docs/manual/mod/mod_log_config.html.ko.euc-kr | 306 ++-- docs/manual/mod/mod_log_config.html.tr.utf8 | 362 ++--- docs/manual/mod/mod_log_debug.html.en | 94 +- docs/manual/mod/mod_log_debug.xml | 6 +- docs/manual/mod/mod_log_forensic.html.en | 92 +- docs/manual/mod/mod_log_forensic.html.ja.utf8 | 100 +- docs/manual/mod/mod_log_forensic.html.tr.utf8 | 100 +- docs/manual/mod/mod_logio.html.en | 34 +- docs/manual/mod/mod_logio.html.ja.utf8 | 36 +- docs/manual/mod/mod_logio.html.ko.euc-kr | 36 +- docs/manual/mod/mod_logio.html.tr.utf8 | 34 +- docs/manual/mod/mod_lua.html.en | 1250 +++++++-------- docs/manual/mod/mod_lua.html.fr | 1346 ++++++++-------- docs/manual/mod/mod_lua.xml | 10 +- docs/manual/mod/mod_macro.html.en | 156 +- docs/manual/mod/mod_macro.html.fr | 152 +- docs/manual/mod/mod_macro.xml | 6 +- docs/manual/mod/mod_mime.html.en | 276 ++-- docs/manual/mod/mod_mime.html.ja.utf8 | 272 ++-- docs/manual/mod/mod_mime.xml | 12 +- docs/manual/mod/mod_mime_magic.html.en | 44 +- docs/manual/mod/mod_negotiation.html.en | 224 +-- docs/manual/mod/mod_negotiation.html.fr | 256 +-- docs/manual/mod/mod_negotiation.html.ja.utf8 | 228 +-- docs/manual/mod/mod_nw_ssl.html.en | 2 +- docs/manual/mod/mod_policy.html.en | 368 ++--- docs/manual/mod/mod_policy.xml | 8 +- docs/manual/mod/mod_privileges.html.en | 118 +- docs/manual/mod/mod_proxy.html.en | 674 ++++---- docs/manual/mod/mod_proxy.html.fr | 790 ++++----- docs/manual/mod/mod_proxy.html.ja.utf8 | 400 ++--- docs/manual/mod/mod_proxy.xml | 10 +- docs/manual/mod/mod_proxy_ajp.html.ja.utf8 | 8 +- docs/manual/mod/mod_proxy_balancer.html.en | 2 +- .../mod/mod_proxy_balancer.html.ja.utf8 | 8 +- docs/manual/mod/mod_proxy_balancer.xml | 2 +- docs/manual/mod/mod_proxy_connect.html.en | 50 +- .../manual/mod/mod_proxy_connect.html.ja.utf8 | 2 +- docs/manual/mod/mod_proxy_express.html.en | 2 +- docs/manual/mod/mod_proxy_fcgi.html.en | 2 +- docs/manual/mod/mod_proxy_fcgi.xml | 2 +- docs/manual/mod/mod_proxy_ftp.html.en | 114 +- docs/manual/mod/mod_proxy_html.html.en | 2 +- docs/manual/mod/mod_proxy_http.html.fr | 8 +- docs/manual/mod/mod_proxy_scgi.html.en | 84 +- docs/manual/mod/mod_proxy_wstunnel.html.en | 2 +- docs/manual/mod/mod_ratelimit.html.en | 2 +- docs/manual/mod/mod_ratelimit.xml | 2 +- docs/manual/mod/mod_reflector.html.en | 52 +- docs/manual/mod/mod_reflector.xml | 4 +- docs/manual/mod/mod_remoteip.html.en | 84 +- docs/manual/mod/mod_remoteip.html.fr | 104 +- docs/manual/mod/mod_reqtimeout.html.en | 90 +- docs/manual/mod/mod_request.html.en | 2 +- docs/manual/mod/mod_request.html.tr.utf8 | 2 +- docs/manual/mod/mod_rewrite.html.en | 74 +- docs/manual/mod/mod_rewrite.html.fr | 90 +- docs/manual/mod/mod_rewrite.xml | 2 +- docs/manual/mod/mod_sed.html.en | 56 +- docs/manual/mod/mod_sed.html.fr | 76 +- docs/manual/mod/mod_session.html.en | 276 ++-- docs/manual/mod/mod_session_cookie.html.en | 38 +- docs/manual/mod/mod_session_crypto.html.en | 46 +- docs/manual/mod/mod_session_dbd.html.en | 160 +- docs/manual/mod/mod_setenvif.html.en | 2 +- docs/manual/mod/mod_setenvif.html.fr | 2 +- docs/manual/mod/mod_setenvif.html.ja.utf8 | 2 +- docs/manual/mod/mod_setenvif.html.ko.euc-kr | 2 +- docs/manual/mod/mod_setenvif.html.tr.utf8 | 2 +- docs/manual/mod/mod_so.html.en | 94 +- docs/manual/mod/mod_so.html.fr | 112 +- docs/manual/mod/mod_so.html.ja.utf8 | 104 +- docs/manual/mod/mod_so.html.ko.euc-kr | 98 +- docs/manual/mod/mod_so.html.tr.utf8 | 112 +- docs/manual/mod/mod_speling.html.en | 2 +- docs/manual/mod/mod_speling.html.ja.utf8 | 2 +- docs/manual/mod/mod_speling.html.ko.euc-kr | 2 +- docs/manual/mod/mod_ssl.html.en | 398 ++--- docs/manual/mod/mod_ssl_ct.html.en | 360 ++--- docs/manual/mod/mod_status.html.en | 2 +- docs/manual/mod/mod_status.html.fr | 8 +- docs/manual/mod/mod_status.html.ja.utf8 | 8 +- docs/manual/mod/mod_status.html.ko.euc-kr | 8 +- docs/manual/mod/mod_status.html.tr.utf8 | 8 +- docs/manual/mod/mod_status.xml | 2 +- docs/manual/mod/mod_substitute.html.en | 10 +- docs/manual/mod/mod_substitute.xml | 8 +- docs/manual/mod/mod_suexec.html.en | 2 +- docs/manual/mod/mod_suexec.html.ja.utf8 | 2 +- docs/manual/mod/mod_suexec.html.ko.euc-kr | 2 +- docs/manual/mod/mod_suexec.html.tr.utf8 | 2 +- docs/manual/mod/mod_systemd.html.en | 2 +- docs/manual/mod/mod_unique_id.html.fr | 8 +- docs/manual/mod/mod_unique_id.html.ja.utf8 | 8 +- docs/manual/mod/mod_unique_id.html.ko.euc-kr | 8 +- docs/manual/mod/mod_unixd.html.en | 2 +- docs/manual/mod/mod_unixd.html.tr.utf8 | 2 +- docs/manual/mod/mod_userdir.html.en | 2 +- docs/manual/mod/mod_userdir.html.ja.utf8 | 2 +- docs/manual/mod/mod_userdir.html.ko.euc-kr | 2 +- docs/manual/mod/mod_userdir.html.tr.utf8 | 2 +- docs/manual/mod/mod_usertrack.html.en | 26 +- docs/manual/mod/mod_version.html.en | 2 +- docs/manual/mod/mod_version.html.ja.utf8 | 2 +- docs/manual/mod/mod_version.html.ko.euc-kr | 2 +- docs/manual/mod/mod_vhost_alias.html.en | 180 +-- docs/manual/mod/mod_vhost_alias.html.tr.utf8 | 170 +- docs/manual/mod/mod_watchdog.html.en | 2 +- docs/manual/mod/mod_xml2enc.html.en | 104 +- docs/manual/mod/mpm_common.html.de | 2 +- docs/manual/mod/mpm_common.html.en | 2 +- docs/manual/mod/mpm_common.html.ja.utf8 | 2 +- docs/manual/mod/mpm_common.html.tr.utf8 | 2 +- docs/manual/mod/mpm_netware.html.en | 2 +- docs/manual/mod/prefork.html.de | 94 +- docs/manual/mod/prefork.html.en | 86 +- docs/manual/mod/prefork.html.ja.utf8 | 100 +- docs/manual/mod/prefork.html.tr.utf8 | 92 +- docs/manual/mod/worker.html.de | 10 +- docs/manual/mod/worker.html.ja.utf8 | 10 +- docs/manual/mod/worker.html.tr.utf8 | 10 +- docs/manual/platform/windows.html.en | 10 +- docs/manual/platform/windows.xml | 10 +- docs/manual/rewrite/access.html.en | 4 +- docs/manual/rewrite/access.xml | 4 +- docs/manual/rewrite/remapping.html.en | 6 +- docs/manual/rewrite/remapping.xml | 23 +- docs/manual/rewrite/vhosts.html.en | 2 +- docs/manual/rewrite/vhosts.xml | 2 +- docs/manual/sections.html.en | 44 +- docs/manual/sections.xml | 44 +- docs/manual/vhosts/mass.html.en | 4 +- docs/manual/vhosts/mass.xml | 4 +- 361 files changed, 16923 insertions(+), 16916 deletions(-) diff --git a/docs/manual/developer/lua.html.en b/docs/manual/developer/lua.html.en index f81d36503c..beec032f7f 100644 --- a/docs/manual/developer/lua.html.en +++ b/docs/manual/developer/lua.html.en @@ -456,10 +456,10 @@ end groups with different permissions: 

LuaAuthzProvider rights /path/to/lua/script.lua rights_handler
-<Directory /www/private>
+<Directory "/www/private">
     Require rights member
 </Directory>
-<Directory /www/admin>
+<Directory "/www/admin">
     Require rights admin
 </Directory>
diff --git a/docs/manual/developer/lua.xml b/docs/manual/developer/lua.xml index 06d9087624..c85b445a60 100644 --- a/docs/manual/developer/lua.xml +++ b/docs/manual/developer/lua.xml @@ -472,10 +472,10 @@ end

LuaAuthzProvider rights /path/to/lua/script.lua rights_handler -<Directory /www/private> +<Directory "/www/private"> Require rights member </Directory> -<Directory /www/admin> +<Directory "/www/admin"> Require rights admin </Directory> diff --git a/docs/manual/env.html.en b/docs/manual/env.html.en index 4df20490d8..23b95e0025 100644 --- a/docs/manual/env.html.en +++ b/docs/manual/env.html.en @@ -484,7 +484,7 @@ CustomLog logs/access_log common env=!image-request 
SetEnvIf Referer "^http://www\.example\.com/" local_referal
 # Allow browsers that do not send Referer info
 SetEnvIf Referer "^$" local_referal
-<Directory /web/images>
+<Directory "/web/images">
     Require env local_referal
 </Directory>
diff --git a/docs/manual/env.xml b/docs/manual/env.xml index 5bfefb285f..d4375cf688 100644 --- a/docs/manual/env.xml +++ b/docs/manual/env.xml @@ -526,7 +526,7 @@ CustomLog logs/access_log common env=!image-request SetEnvIf Referer "^http://www\.example\.com/" local_referal # Allow browsers that do not send Referer info SetEnvIf Referer "^$" local_referal -<Directory /web/images> +<Directory "/web/images"> Require env local_referal </Directory> diff --git a/docs/manual/expr.html.en b/docs/manual/expr.html.en index 7defa17d22..46d0565c52 100644 --- a/docs/manual/expr.html.en +++ b/docs/manual/expr.html.en @@ -546,7 +546,7 @@ listfunction ::= listfuncname "(" word ")"(" word ")" </If> # Check result of URI mapping by running in Directory context with -f -<Directory /var/www> +<Directory "/var/www"> AddEncoding x-gzip gz <If "-f '%{REQUEST_FILENAME}.unzipme' && ! %{HTTP:Accept-Encoding} =~ /gzip/"> SetOutputFilter INFLATE diff --git a/docs/manual/handler.html.en b/docs/manual/handler.html.en index 5f1700350e..72683d8fd3 100644 --- a/docs/manual/handler.html.en +++ b/docs/manual/handler.html.en @@ -117,7 +117,7 @@ AddHandler add-footer .html the send-as-is handler, regardless of their filename extensions.

- 
<Directory /web/htdocs/asis>
+      
<Directory "/web/htdocs/asis">
     SetHandler send-as-is
 </Directory>

 
diff --git a/docs/manual/handler.xml b/docs/manual/handler.xml
index 98dc9599bf..fd37d5603e 100644
--- a/docs/manual/handler.xml
+++ b/docs/manual/handler.xml
@@ -127,7 +127,7 @@ AddHandler add-footer .html
       filename extensions.

 
       
-<Directory /web/htdocs/asis>
+<Directory "/web/htdocs/asis">
     SetHandler send-as-is
 </Directory>
       
diff --git a/docs/manual/howto/cgi.html.en b/docs/manual/howto/cgi.html.en
index c47a64232f..5a7c34f828 100644
--- a/docs/manual/howto/cgi.html.en
+++ b/docs/manual/howto/cgi.html.en
@@ -137,7 +137,7 @@
       file, to specify that CGI execution was permitted in a particular
       directory:

 
-      
<Directory /usr/local/apache2/htdocs/somedir>
+      
<Directory "/usr/local/apache2/htdocs/somedir">
     Options +ExecCGI
 </Directory>

 
@@ -167,7 +167,7 @@
       .cgi in users' directories, you can use the
       following configuration.

 
-      
<Directory /home/*/public_html>
+      
<Directory "/home/*/public_html">
     Options +ExecCGI
     AddHandler cgi-script .cgi
 </Directory>

@@ -177,7 +177,7 @@
       a user's directory where everything will be treated as a CGI
       program, you can use the following.

 
-      
<Directory /home/*/public_html/cgi-bin>
+      
<Directory "/home/*/public_html/cgi-bin">
     Options ExecCGI
     SetHandler cgi-script
 </Directory>

diff --git a/docs/manual/howto/cgi.xml b/docs/manual/howto/cgi.xml
index bf6f4dc6c8..9ca0e6b436 100644
--- a/docs/manual/howto/cgi.xml
+++ b/docs/manual/howto/cgi.xml
@@ -146,7 +146,7 @@
       directory:

 
       
-<Directory /usr/local/apache2/htdocs/somedir>
+<Directory "/usr/local/apache2/htdocs/somedir">
     Options +ExecCGI
 </Directory>
       
@@ -179,7 +179,7 @@
       following configuration.

 
       
-<Directory /home/*/public_html>
+<Directory "/home/*/public_html">
     Options +ExecCGI
     AddHandler cgi-script .cgi
 </Directory>
@@ -190,7 +190,7 @@
       program, you can use the following.

 
       
-<Directory /home/*/public_html/cgi-bin>
+<Directory "/home/*/public_html/cgi-bin">
     Options ExecCGI
     SetHandler cgi-script
 </Directory>
diff --git a/docs/manual/howto/public_html.html.en b/docs/manual/howto/public_html.html.en
index fa55b63edb..a329b6e13a 100644
--- a/docs/manual/howto/public_html.html.en
+++ b/docs/manual/howto/public_html.html.en
@@ -154,7 +154,7 @@
     directive to make a particular subdirectory of a user's home directory
     cgi-enabled.

 
-    
<Directory /home/*/public_html/cgi-bin/>
+    
<Directory "/home/*/public_html/cgi-bin/">
     Options ExecCGI
     SetHandler cgi-script
 </Directory>

diff --git a/docs/manual/howto/public_html.xml b/docs/manual/howto/public_html.xml
index fbcef0fb7f..063501378b 100644
--- a/docs/manual/howto/public_html.xml
+++ b/docs/manual/howto/public_html.xml
@@ -154,7 +154,7 @@
     cgi-enabled.

 
     
-<Directory /home/*/public_html/cgi-bin/>
+<Directory "/home/*/public_html/cgi-bin/">
     Options ExecCGI
     SetHandler cgi-script
 </Directory>
diff --git a/docs/manual/misc/perf-scaling.html.en b/docs/manual/misc/perf-scaling.html.en
index 6a794830e0..be5acff59e 100644
--- a/docs/manual/misc/perf-scaling.html.en
+++ b/docs/manual/misc/perf-scaling.html.en
@@ -1285,8 +1285,7 @@ Swap:       3903784      12540  3891244

       ServerName blog.sandla.org:8001
       ServerAdmin sander@temme.net
       DocumentRoot "/home/sctemme/inst/blog/httpd/htdocs"
-      <Directory
-      "/home/sctemme/inst/blog/httpd/htdocs">
+      <Directory "/home/sctemme/inst/blog/httpd/htdocs">
           Options +Indexes
           Require all granted
           RewriteEngine on
@@ -1418,7 +1417,7 @@ CacheMaxExpire 21600

                     Unfortunately there does currently not exist a way to cache
                     these headers. 
                 

-
<FilesMatch \.(jpe?g|png|gif|js|css|x?html|xml)>
+
<FilesMatch "\.(jpe?g|png|gif|js|css|x?html|xml)">
     FileETag None
 </FilesMatch>

 
diff --git a/docs/manual/misc/perf-scaling.xml b/docs/manual/misc/perf-scaling.xml
index 6fcb818da0..cb88b8bf11 100644
--- a/docs/manual/misc/perf-scaling.xml
+++ b/docs/manual/misc/perf-scaling.xml
@@ -1284,8 +1284,7 @@ Listen *:8001
       ServerName blog.sandla.org:8001
       ServerAdmin sander@temme.net
       DocumentRoot "/home/sctemme/inst/blog/httpd/htdocs"
-      <Directory
-      "/home/sctemme/inst/blog/httpd/htdocs">
+      <Directory "/home/sctemme/inst/blog/httpd/htdocs">
           Options +Indexes
           Require all granted
           RewriteEngine on
@@ -1420,7 +1419,7 @@ CacheMaxExpire 21600
                     these headers. 
                 

 
-<FilesMatch \.(jpe?g|png|gif|js|css|x?html|xml)>
+<FilesMatch "\.(jpe?g|png|gif|js|css|x?html|xml)">
     FileETag None
 </FilesMatch>
 
diff --git a/docs/manual/misc/perf-tuning.html.en b/docs/manual/misc/perf-tuning.html.en
index 7b529c7b52..4f36d3676f 100644
--- a/docs/manual/misc/perf-tuning.html.en
+++ b/docs/manual/misc/perf-tuning.html.en
@@ -132,7 +132,7 @@
       using these directives, if possible.

 
       
Note that it's possible to scope the directives, such as
-      within a <Location /server-status> section.
+      within a <Location "/server-status"> section.
       In this case the DNS lookups are only performed on requests
       matching the criteria. Here's an example which disables lookups
       except for .html and .cgi files:

@@ -160,7 +160,7 @@
       filename component. For example, if you had:

 
       
DocumentRoot /www/htdocs
-<Directory />
+<Directory "/">
   Options SymLinksIfOwnerMatch
 </Directory>

 
@@ -174,11 +174,11 @@
       security checking you can do something like this:

 
       
DocumentRoot /www/htdocs
-<Directory />
+<Directory "/">
   Options FollowSymLinks
 </Directory>
 
-<Directory /www/htdocs>
+<Directory "/www/htdocs">
   Options -FollowSymLinks +SymLinksIfOwnerMatch
 </Directory>

 
@@ -204,7 +204,7 @@
       example,

 
       
DocumentRoot /www/htdocs
-<Directory />
+<Directory "/">
   AllowOverride all
 </Directory>

 
diff --git a/docs/manual/misc/perf-tuning.xml b/docs/manual/misc/perf-tuning.xml
index bb44c33a82..6853e68e27 100644
--- a/docs/manual/misc/perf-tuning.xml
+++ b/docs/manual/misc/perf-tuning.xml
@@ -147,7 +147,7 @@
       using these directives, if possible.

 
       
Note that it's possible to scope the directives, such as
-      within a <Location /server-status> section.
+      within a <Location "/server-status"> section.
       In this case the DNS lookups are only performed on requests
       matching the criteria. Here's an example which disables lookups
       except for .html and .cgi files:

@@ -177,7 +177,7 @@ HostnameLookups off
 
       
 DocumentRoot /www/htdocs
-<Directory />
+<Directory "/">
   Options SymLinksIfOwnerMatch
 </Directory>
       
@@ -192,11 +192,11 @@ DocumentRoot /www/htdocs
 
       
 DocumentRoot /www/htdocs
-<Directory />
+<Directory "/">
   Options FollowSymLinks
 </Directory>
 
-<Directory /www/htdocs>
+<Directory "/www/htdocs">
   Options -FollowSymLinks +SymLinksIfOwnerMatch
 </Directory>
       
@@ -223,7 +223,7 @@ DocumentRoot /www/htdocs
 
       
 DocumentRoot /www/htdocs
-<Directory />
+<Directory "/">
   AllowOverride all
 </Directory>
       
diff --git a/docs/manual/misc/security_tips.html.en b/docs/manual/misc/security_tips.html.en
index 522083f665..b3da0c96cf 100644
--- a/docs/manual/misc/security_tips.html.en
+++ b/docs/manual/misc/security_tips.html.en
@@ -334,7 +334,7 @@
 
     
In the server configuration file, put

 
-    
<Directory />
+    
<Directory "/">
     AllowOverride None
 </Directory>

 
@@ -366,7 +366,7 @@
     work around this, add the following block to your server's
     configuration:

 
-    
<Directory />
+    
<Directory "/">
     Require all denied
 </Directory>

 
@@ -375,17 +375,17 @@
     appropriate Directory blocks to
     allow access only in those areas you wish. For example,

 
-    
<Directory /usr/users/*/public_html>
+    
<Directory "/usr/users/*/public_html">
     Require all granted
 </Directory>
-<Directory /usr/local/httpd>
+<Directory "/usr/local/httpd">
     Require all granted
 </Directory>

 
 
     
Pay particular attention to the interactions of Location and Directory directives; for instance, even
-    if <Directory /> denies access, a 
-    <Location /> directive might overturn it.

+    if <Directory "/"> denies access, a 
+    <Location "/"> directive might overturn it.

 
     
Also be wary of playing games with the UserDir directive; setting it to
     something like ./ would have the same effect, for root, as
diff --git a/docs/manual/misc/security_tips.xml b/docs/manual/misc/security_tips.xml
index 5664ff9d3e..af003eb889 100644
--- a/docs/manual/misc/security_tips.xml
+++ b/docs/manual/misc/security_tips.xml
@@ -328,7 +328,7 @@
     
In the server configuration file, put

 
     
-<Directory />
+<Directory "/">
     AllowOverride None
 </Directory>
     
@@ -361,7 +361,7 @@
     configuration:

 
     
-<Directory />
+<Directory "/">
     Require all denied
 </Directory>
     
@@ -371,10 +371,10 @@
     allow access only in those areas you wish. For example,

 
     
-<Directory /usr/users/*/public_html>
+<Directory "/usr/users/*/public_html">
     Require all granted
 </Directory>
-<Directory /usr/local/httpd>
+<Directory "/usr/local/httpd">
     Require all granted
 </Directory>
     
@@ -382,8 +382,8 @@
     
Pay particular attention to the interactions of Location and Directory directives; for instance, even
-    if <Directory /> denies access, a 
-    <Location /> directive might overturn it.

+    if <Directory "/"> denies access, a 
+    <Location "/"> directive might overturn it.

 
     
Also be wary of playing games with the UserDir directive; setting it to
diff --git a/docs/manual/mod/core.html.de b/docs/manual/mod/core.html.de
index c574b61e1b..c287b322a3 100644
--- a/docs/manual/mod/core.html.de
+++ b/docs/manual/mod/core.html.de
@@ -124,6 +124,7 @@ Servers
 
  •  Warning
    • 
 
 
+
 
    top
    
 
    AcceptFilter-Direktive
    
 
@@ -3660,7 +3661,6 @@ IP-Adressen angewendet werden
    
 
    Die Dokumentation zu dieser Direktive wurde
             noch nicht bersetzt. Bitte schauen Sie in die englische
             Version.
    
-
 
 
    
 
    Verfgbare Sprachen:  de  |
diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en
index ce3ff4da0b..ae927b47c4 100644
--- a/docs/manual/mod/core.html.en
+++ b/docs/manual/mod/core.html.en
@@ -121,6 +121,7 @@ available
 
  •  Warning
    • 
 
 
    
+
 
    top
    
 
    AcceptFilter Directive
    
 
@@ -294,7 +295,7 @@ AcceptFilter https data/usr/local/.acl and /usr/local/web/.acl
     for directives, unless they have been disabled with
    
 
-    
    <Directory />
+    
    <Directory "/">
     AllowOverride None
 </Directory>
    
 
@@ -533,7 +534,7 @@ NoDecode option available in 2.3.12 and later.
 
     
    For security and performance reasons, do not set
     AllowOverride to anything other than None
-    in your <Directory /> block. Instead, find (or
+    in your <Directory "/"> block. Instead, find (or
     create) the <Directory> block that refers to the
     directory where you're actually planning to place a
     .htaccess file.
    
@@ -836,9 +837,9 @@ named file-system directory, sub-directories, and their contents.
     any single character, and * matches any sequences of
     characters. You may also use [] character ranges. None
     of the wildcards match a `/' character, so <Directory
-    /*/public_html> will not match
+    "/*/public_html"> will not match
     /home/user/public_html, but <Directory
-    /home/*/public_html> will match. Example:
    
+    "/home/*/public_html"> will match. Example:
    
 
     
    <Directory "/usr/local/httpd/htdocs">
   Options Indexes FollowSymLinks
@@ -876,7 +877,7 @@ named file-system directory, sub-directories, and their contents.
     first, interspersed with the directives from the .htaccess files. For example,
     with
    
 
-    
    <Directory />
+    
    <Directory "/">
   AllowOverride None
 </Directory>
 
@@ -918,12 +919,12 @@ named file-system directory, sub-directories, and their contents.
     be applied.
    
 
    
    Note that the default access for
-    <Directory /> is to permit all access.
+    <Directory "/"> is to permit all access.
     This means that Apache httpd will serve any file mapped from an URL. It is
     recommended that you change this with a block such
     as
    
 
-    
    <Directory />
+    
    <Directory "/">
   Require all denied
 </Directory>
    
 
@@ -991,7 +992,7 @@ the contents of file-system directories matching a regular expression.
     mod_rewrite. In order to prevent confusion, numbered
     (unnamed) backreferences are ignored. Use named groups instead.
    
 
-
    <DirectoryMatch ^/var/www/combined/(?<sitename>[^/]+)>
+
    <DirectoryMatch "^/var/www/combined/(?<sitename>[^/]+)">
     Require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
 </DirectoryMatch>
    
 
@@ -1335,7 +1336,7 @@ ErrorDocument 403 /cgi-bin/forbidden.pl?referrer=%{escape:%{HTTP_REFERER}}
    
 
     
    ErrorDocument 404 /cgi-bin/bad_urls.pl
 
-<Directory /web/docs>
+<Directory "/web/docs">
   ErrorDocument 404 default
 </Directory>
    
 
@@ -1817,7 +1818,7 @@ filenames
     mod_rewrite. In order to prevent confusion, numbered
     (unnamed) backreferences are ignored. Use named groups instead.
    
 
-
    <FilesMatch ^(?<sitename>[^/]+)>
+
    <FilesMatch "^(?<sitename>[^/]+)">
     require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
 </FilesMatch>
    
 
@@ -1862,12 +1863,12 @@ media type in the HTTP Content-Type header field
     by using the value of None:
    
 
     
    # force all files to be image/gif:
-<Location /images>
+<Location "/images">
   ForceType image/gif
 </Location>
 
 # but normal mime-type associations here:
-<Location /images/mixed>
+<Location "/images/mixed">
   ForceType None
 </Location>
    
 
@@ -2649,7 +2650,7 @@ URLs
     /private1, /private1/ and /private1/file.txt will have the enclosed
     directives applied, but /private1other would not.
     
    
-    
    <Location /private1>
+    
    <Location "/private1">
     #  ...
 </Location>
    
 
@@ -2658,7 +2659,7 @@ URLs
     /private2/ and /private2/file.txt will have the enclosed
     directives applied, but /private2 and /private2other would not.
     
    
-    
    <Location /private2/>
+    
    <Location "/private2/">
     # ...
 </Location>
    
 
@@ -2668,7 +2669,7 @@ URLs
     
    Use <Location> to apply
     directives to content that lives outside the filesystem.  For
     content that lives in the filesystem, use <Directory> and <Files>.  An exception is
-    <Location />, which is an easy way to
+    <Location "/">, which is an easy way to
     apply a configuration to the entire server.
    
     
    
 
@@ -2704,7 +2705,7 @@ URLs
     directive. For example, to enable status requests, but allow them
     only from browsers at example.com, you might use:
    
 
-    
    <Location /status>
+    
    <Location "/status">
   SetHandler server-status
   Require host example.com
 </Location>
    
@@ -2720,12 +2721,12 @@ URLs
       directive and the regex version of <Location> require you to explicitly specify multiple
       slashes if that is your intention.
    
 
-      
    For example, <LocationMatch ^/abc> would match
+      
    For example, <LocationMatch "^/abc"> would match
       the request URL /abc but not the request URL 
       //abc. The (non-regex) <Location> directive behaves similarly when used for
       proxy requests. But when (non-regex) <Location> is used for non-proxy requests it will
       implicitly match multiple slashes with a single slash. For example,
-      if you specify <Location /abc/def> and the
+      if you specify <Location "/abc/def"> and the
       request is to /abc//def then it will match.
    
     
 
@@ -2778,7 +2779,7 @@ matching URLs
     mod_rewrite. In order to prevent confusion, numbered
     (unnamed) backreferences are ignored. Use named groups instead.
    
 
-
    <LocationMatch ^/combined/(?<sitename>[^/]+)>
+
    <LocationMatch "^/combined/(?<sitename>[^/]+)">
     require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
 </LocationMatch>
    
 
@@ -4212,7 +4213,7 @@ handler
     
    You could also use this directive to configure a particular
     handler for files with a particular file extension. For example:
    
 
-    
    <FilesMatch \.php$>
+    
    <FilesMatch "\.php$">
     SetHandler application/x-httpd-php
 </FilesMatch>
    
 
@@ -4639,7 +4640,6 @@ hostname or IP address
 
 
 
-
 
 
    
 
    Available Languages:  de  |
diff --git a/docs/manual/mod/core.html.es b/docs/manual/mod/core.html.es
index 98d1915621..61acd5605a 100644
--- a/docs/manual/mod/core.html.es
+++ b/docs/manual/mod/core.html.es
@@ -124,6 +124,7 @@
 
  •  Warning
    • 
 
 
    
+
 
    top
    
 
    AcceptFilter Directiva
    
 
    
     
    
@@ -4359,7 +4360,6 @@ hostname or IP address
    
 
    The documentation for this directive has
             not been translated yet. Please have a look at the English
             version.
    
-
 
 
    
 
    Idiomas disponibles:  de  |
diff --git a/docs/manual/mod/core.html.fr b/docs/manual/mod/core.html.fr
index ea2eb10b58..8a3c7dcd7b 100644
--- a/docs/manual/mod/core.html.fr
+++ b/docs/manual/mod/core.html.fr
@@ -123,6 +123,7 @@ disponibles
 
  •  Warning
    • 
 
 
    
+
 
    top
    
 
    Directive AcceptFilter
    
 
@@ -4960,7 +4961,6 @@ Apache.
-
 
    
 
    Langues Disponibles:  de  |
diff --git a/docs/manual/mod/core.html.ja.utf8 b/docs/manual/mod/core.html.ja.utf8
index f8aee4e117..00e11a9aca 100644
--- a/docs/manual/mod/core.html.ja.utf8
+++ b/docs/manual/mod/core.html.ja.utf8
@@ -124,6 +124,7 @@
 
  •  Warning
    • 
 
 
    
+
 
    top
    AcceptFilter ディレクティブ
    
 
    
 
 
 
 
 
    
@@ -3575,7 +3576,6 @@ of a request or the last 63, assuming the request itself is greater than
 
    このディレクティブの解説文書は
             まだ翻訳されていません。英語版をご覧ください。
             
    
-
 
 
    
 
    翻訳済み言語:  de  |
diff --git a/docs/manual/mod/core.html.tr.utf8 b/docs/manual/mod/core.html.tr.utf8
index 2466055c6e..06df756384 100644
--- a/docs/manual/mod/core.html.tr.utf8
+++ b/docs/manual/mod/core.html.tr.utf8
@@ -122,6 +122,7 @@
 
  •  Warning
    • 
 
 
    
+
 
    top
    
 
    AcceptFilter Yönergesi
    
 
@@ -4510,7 +4511,6 @@ gerçekleşmesi için sunucunun geçmesini bekleyeceği süre.
    
 
    Uyumluluk:2.5 and later
    
 
    Bu yönergenin belgesi henüz Türkçeye çevrilmedi.
             Lütfen İngilizce sürümüne bakınız.
    
-
 
 
    
 
    Mevcut Diller:  de  |
diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml
index ffca5551de..113103e4e6 100644
--- a/docs/manual/mod/core.xml
+++ b/docs/manual/mod/core.xml
@@ -204,7 +204,7 @@ AcceptFilter https data
     for directives, unless they have been disabled with
    
 
     
-<Directory />
+<Directory "/">
     AllowOverride None
 </Directory>
     
@@ -472,7 +472,7 @@ NoDecode option available in 2.3.12 and later.
 
     
    For security and performance reasons, do not set
     AllowOverride to anything other than None
-    in your <Directory /> block. Instead, find (or
+    in your <Directory "/"> block. Instead, find (or
     create) the <Directory> block that refers to the
     directory where you're actually planning to place a
     .htaccess file.
    
@@ -774,9 +774,9 @@ named file-system directory, sub-directories, and their contents.
     any single character, and * matches any sequences of
     characters. You may also use [] character ranges. None
     of the wildcards match a `/' character, so <Directory
-    /*/public_html> will not match
+    "/*/public_html"> will not match
     /home/user/public_html, but <Directory
-    /home/*/public_html> will match. Example:
    
+    "/home/*/public_html"> will match. Example:
    
 
     
 <Directory "/usr/local/httpd/htdocs">
@@ -819,7 +819,7 @@ named file-system directory, sub-directories, and their contents.
     with
    
 
     
-<Directory />
+<Directory "/">
   AllowOverride None
 </Directory>
 
@@ -862,13 +862,13 @@ named file-system directory, sub-directories, and their contents.
     be applied.
    
 
    
    Note that the default access for
-    <Directory /> is to permit all access.
+    <Directory "/"> is to permit all access.
     This means that Apache httpd will serve any file mapped from an URL. It is
     recommended that you change this with a block such
     as
    
 
     
-<Directory />
+<Directory "/">
   Require all denied
 </Directory>
     
@@ -938,7 +938,7 @@ the contents of file-system directories matching a regular expression.
 
 
-<DirectoryMatch ^/var/www/combined/(?<sitename>[^/]+)>
+<DirectoryMatch "^/var/www/combined/(?<sitename>[^/]+)">
     Require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
 </DirectoryMatch>
 
@@ -1286,7 +1286,7 @@ ErrorDocument 403 /cgi-bin/forbidden.pl?referrer=%{escape:%{HTTP_REFERER}}
     
 ErrorDocument 404 /cgi-bin/bad_urls.pl
 
-<Directory /web/docs>
+<Directory "/web/docs">
   ErrorDocument 404 default
 </Directory>
     
@@ -1810,7 +1810,7 @@ filenames
     (unnamed) backreferences are ignored. Use named groups instead.
    
 
 
-<FilesMatch ^(?<sitename>[^/]+)>
+<FilesMatch "^(?<sitename>[^/]+)">
     require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
 </FilesMatch>
 
@@ -1853,12 +1853,12 @@ media type in the HTTP Content-Type header field
 
     
 # force all files to be image/gif:
-<Location /images>
+<Location "/images">
   ForceType image/gif
 </Location>
 
 # but normal mime-type associations here:
-<Location /images/mixed>
+<Location "/images/mixed">
   ForceType None
 </Location>
     
@@ -2651,7 +2651,7 @@ URLs
     directives applied, but /private1other would not.
     
    
     
-<Location /private1>
+<Location "/private1">
     #  ...
 </Location>
     
@@ -2661,7 +2661,7 @@ URLs
     directives applied, but /private2 and /private2other would not.
     
    
     
-<Location /private2/>
+<Location "/private2/">
     # ...
 </Location>
     
@@ -2674,7 +2674,7 @@ URLs
     content that lives in the filesystem, use Directory and Files.  An exception is
-    <Location />, which is an easy way to
+    <Location "/">, which is an easy way to
     apply a configuration to the entire server.
    
         
 
@@ -2714,7 +2714,7 @@ URLs
     only from browsers at example.com, you might use:
    
 
     
-<Location /status>
+<Location "/status">
   SetHandler server-status
   Require host example.com
 </Location>
@@ -2731,14 +2731,14 @@ URLs
       >Location require you to explicitly specify multiple
       slashes if that is your intention.
    
 
-      
    For example, <LocationMatch ^/abc> would match
+      
    For example, <LocationMatch "^/abc"> would match
       the request URL /abc but not the request URL 
       //abc. The (non-regex) Location directive behaves similarly when used for
       proxy requests. But when (non-regex) Location is used for non-proxy requests it will
       implicitly match multiple slashes with a single slash. For example,
-      if you specify <Location /abc/def> and the
+      if you specify <Location "/abc/def"> and the
       request is to /abc//def then it will match.
    
     
 
@@ -2791,7 +2791,7 @@ matching URLs
     (unnamed) backreferences are ignored. Use named groups instead.
    
 
 
-<LocationMatch ^/combined/(?<sitename>[^/]+)>
+<LocationMatch "^/combined/(?<sitename>[^/]+)">
     require ldap-group cn=%{env:MATCH_SITENAME},ou=combined,o=Example
 </LocationMatch>
 
@@ -4177,7 +4177,7 @@ handler
     handler for files with a particular file extension. For example:
    
 
     
-<FilesMatch \.php$>
+<FilesMatch "\.php$">
     SetHandler application/x-httpd-php
 </FilesMatch>
     
diff --git a/docs/manual/mod/event.html.en b/docs/manual/mod/event.html.en
index 6643e05365..964fca8cd7 100644
--- a/docs/manual/mod/event.html.en
+++ b/docs/manual/mod/event.html.en
@@ -80,58 +80,6 @@ of consuming threads only for connections with active processing
 
  • The worker MPM
    • 
 
    
 
    top
    
-
    AsyncRequestWorkerFactor Directive
    
-
-
-
-
-
-
-
-
-
    Description:Limit concurrent connections per process
    Syntax:AsyncRequestWorkerFactor factor
    Default:2
    Context:server config
    Status:MPM
    Module:event
    Compatibility:Available in version 2.3.13 and later
    
-    
    The event MPM handles some connections in an asynchronous way, where
-    request worker threads are only allocated for short periods of time as
-    needed, and other connections with one request worker thread reserved per
-    connection. This can lead to situations where all workers are tied up and
-    no worker thread is available to handle new work on established async
-    connections.
    
-
-    
    To mitigate this problem, the event MPM does two things: Firstly, it
-    limits the number of connections accepted per process, depending on the
-    number of idle request workers. Secondly, if all workers are busy, it will
-    close connections in keep-alive state even if the keep-alive timeout has
-    not expired. This allows the respective clients to reconnect to a
-    different process which may still have worker threads available.
    
-
-    
    This directive can be used to fine-tune the per-process connection
-    limit. A process will only accept new connections if the current number of
-    connections (not counting connections in the "closing" state) is lower
-    than:
    
-
-    
    
-        ThreadsPerChild +
-        (AsyncRequestWorkerFactor *
-        number of idle workers)
-    
    
-
-    
    This means the absolute maximum numbers of concurrent connections is:
    
-
-    
    
-        (AsyncRequestWorkerFactor + 1) *
-        MaxRequestWorkers
-    
    
-
-    
    MaxRequestWorkers was called
-    MaxClients prior to version 2.3.13. The above value
-    shows that the old name did not accurately describe its meaning for the event MPM.
    
-
-    
    AsyncRequestWorkerFactor can take non-integer
-    arguments, e.g "1.5".
    
-
-
-
    
-
    top
    
 
    
 
    How it Works
    
     
    This MPM tries to fix the 'keep alive problem' in HTTP. After a client
@@ -197,6 +145,58 @@ of consuming threads only for connections with active processing
       with support for EPoll.
 
     
+
    
+
    top
    
+
    AsyncRequestWorkerFactor Directive
    
+
+
+
+
+
+
+
+
+
    Description:Limit concurrent connections per process
    Syntax:AsyncRequestWorkerFactor factor
    Default:2
    Context:server config
    Status:MPM
    Module:event
    Compatibility:Available in version 2.3.13 and later
    
+    
    The event MPM handles some connections in an asynchronous way, where
+    request worker threads are only allocated for short periods of time as
+    needed, and other connections with one request worker thread reserved per
+    connection. This can lead to situations where all workers are tied up and
+    no worker thread is available to handle new work on established async
+    connections.
    
+
+    
    To mitigate this problem, the event MPM does two things: Firstly, it
+    limits the number of connections accepted per process, depending on the
+    number of idle request workers. Secondly, if all workers are busy, it will
+    close connections in keep-alive state even if the keep-alive timeout has
+    not expired. This allows the respective clients to reconnect to a
+    different process which may still have worker threads available.
    
+
+    
    This directive can be used to fine-tune the per-process connection
+    limit. A process will only accept new connections if the current number of
+    connections (not counting connections in the "closing" state) is lower
+    than:
    
+
+    
    
+        ThreadsPerChild +
+        (AsyncRequestWorkerFactor *
+        number of idle workers)
+    
    
+
+    
    This means the absolute maximum numbers of concurrent connections is:
    
+
+    
    
+        (AsyncRequestWorkerFactor + 1) *
+        MaxRequestWorkers
+    
    
+
+    
    MaxRequestWorkers was called
+    MaxClients prior to version 2.3.13. The above value
+    shows that the old name did not accurately describe its meaning for the event MPM.
    
+
+    
    AsyncRequestWorkerFactor can take non-integer
+    arguments, e.g "1.5".
    
+
+
 
    
 
 
    
diff --git a/docs/manual/mod/event.html.fr b/docs/manual/mod/event.html.fr
index 7f674fe799..f9cd764124 100644
--- a/docs/manual/mod/event.html.fr
+++ b/docs/manual/mod/event.html.fr
@@ -50,7 +50,11 @@ mobiliser des threads que pour les connexions en cours de traitement
     httpd.
    
 
 
    
-
    Directives
    
+
    Sujets
    
+
    Directives
    
 
-
    Sujets
    
-
    Voir aussi
    
+
    Voir aussi
    
 
    
 
    top
    
-
    Directive AsyncRequestWorkerFactor
    
-
-
-
-
-
-
-
-
-
    Description:Limite le nombre de connexions simultanes par thread
    Syntaxe:AsyncRequestWorkerFactor facteur
    Dfaut:2
    Contexte:configuration du serveur
    Statut:MPM
    Module:event
    Compatibilit:Disponible depuis la version 2.3.13
    
-    
    Le MPM event gre certaines connexions de manire asynchrone ;
-    dans ce cas, les threads traitant la requte sont allous selon les
-    besoins et pour de courtes priodes. Dans les autres cas, un
-    thread est rserv par
-    connexion. Ceci peut conduire  des situations o tous les threads
-    sont saturs et o aucun thread n'est capable d'effectuer de
-    nouvelles tches pour les connexions asynchrones tablies.
    
-
-    
    Pour minimiser les effets de ce problme, le MPM event utilise
-    deux mthodes : tout d'abord, il limite le nombre de connexions
-    simultanes par thread en fonction du nombre de processus
-    inactifs. Ensuite, si tous les processus sont occups, il ferme des
-    connexions permanentes, mme si la limite de dure de la connexion
-    n'a pas t atteinte. Ceci autorise les clients concerns  se
-    reconnecter  un autre processus possdant encore des threads
-    disponibles.
    
-
-    
    Cette directive permet de personnaliser finement la limite du
-    nombre de connexions par thread. Un processus n'acceptera de
-    nouvelles connexions que si le nombre actuel de connexions (sans
-    compter les connexions  l'tat "closing") est
-    infrieur  :
    
-
-    
    
-        ThreadsPerChild +
-        (AsyncRequestWorkerFactor *
-        nombre de threads inactifs)
-    
    
-
-    
    En d'autres termes, le nombre maximum de connexions simultanes
-    sera :
    
-
-    
    
-        (AsyncRequestWorkerFactor + 1) *
-        MaxRequestWorkers
-    
    
-
-    
    La directive MaxRequestWorkers se nommait
-    MaxClients avant la version 2.3.13. La valeur
-    ci-dessus montre que cet ancien nom ne correspondait pas  sa
-    signification exacte pour le MPM event.
    
-
-    
    La directive AsyncRequestWorkerFactor
-    accepte des valeurs d'argument de type non entier, comme "1.5".
    
-
-
-
    
-
    top
    
 
    
 
    Comment tout cela fonctionne
    
     
    Ce MPM essaie de rsoudre le 'problme keep alive' de HTTP.
@@ -217,6 +159,64 @@ mobiliser des threads que pour les connexions en cours de traitement
       avec le support pour EPoll.
 
     
+
    
+
    top
    
+
    Directive AsyncRequestWorkerFactor
    
+
+
+
+
+
+
+
+
+
    Description:Limite le nombre de connexions simultanes par thread
    Syntaxe:AsyncRequestWorkerFactor facteur
    Dfaut:2
    Contexte:configuration du serveur
    Statut:MPM
    Module:event
    Compatibilit:Disponible depuis la version 2.3.13
    
+    
    Le MPM event gre certaines connexions de manire asynchrone ;
+    dans ce cas, les threads traitant la requte sont allous selon les
+    besoins et pour de courtes priodes. Dans les autres cas, un
+    thread est rserv par
+    connexion. Ceci peut conduire  des situations o tous les threads
+    sont saturs et o aucun thread n'est capable d'effectuer de
+    nouvelles tches pour les connexions asynchrones tablies.
    
+
+    
    Pour minimiser les effets de ce problme, le MPM event utilise
+    deux mthodes : tout d'abord, il limite le nombre de connexions
+    simultanes par thread en fonction du nombre de processus
+    inactifs. Ensuite, si tous les processus sont occups, il ferme des
+    connexions permanentes, mme si la limite de dure de la connexion
+    n'a pas t atteinte. Ceci autorise les clients concerns  se
+    reconnecter  un autre processus possdant encore des threads
+    disponibles.
    
+
+    
    Cette directive permet de personnaliser finement la limite du
+    nombre de connexions par thread. Un processus n'acceptera de
+    nouvelles connexions que si le nombre actuel de connexions (sans
+    compter les connexions  l'tat "closing") est
+    infrieur  :
    
+
+    
    
+        ThreadsPerChild +
+        (AsyncRequestWorkerFactor *
+        nombre de threads inactifs)
+    
    
+
+    
    En d'autres termes, le nombre maximum de connexions simultanes
+    sera :
    
+
+    
    
+        (AsyncRequestWorkerFactor + 1) *
+        MaxRequestWorkers
+    
    
+
+    
    La directive MaxRequestWorkers se nommait
+    MaxClients avant la version 2.3.13. La valeur
+    ci-dessus montre que cet ancien nom ne correspondait pas  sa
+    signification exacte pour le MPM event.
    
+
+    
    La directive AsyncRequestWorkerFactor
+    accepte des valeurs d'argument de type non entier, comme "1.5".
    
+
+
 
    
 
    
 
    
diff --git a/docs/manual/mod/mod_access_compat.html.en b/docs/manual/mod/mod_access_compat.html.en
index ce8c254358..9eaf18ffbe 100644
--- a/docs/manual/mod/mod_access_compat.html.en
+++ b/docs/manual/mod/mod_access_compat.html.en
@@ -91,6 +91,7 @@ have been deprecated by the new authz refactoring.  Please see
 
  • mod_authz_host
    • 
 
  • mod_authz_core
    • 
 
    
+
 
    top
    
 
    Allow Directive
    
 
@@ -198,7 +199,7 @@ Allow from 2001:db8::a00:20ff:fea7:ccea/10
     other HTTP request header fields.
    SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in
-<Directory /docroot>
+<Directory "/docroot">
     Order Deny,Allow
     Deny from all
     Allow from env=let_me_in
@@ -358,7 +359,7 @@ Deny from foo.example.org
    
     directives because of its effect on the default access state. For
     example,
    
 
-    
    <Directory /www>
+    
    <Directory "/www">
     Order Allow,Deny
 </Directory>
    
 
@@ -426,11 +427,11 @@ Satisfy Any
    
     is to relax access restrictions for a subdirectory:
     
    
 
-    
    <Directory /var/www/private>
+    
    <Directory "/var/www/private">
     Require valid-user
 </Directory>
 
-<Directory /var/www/private/public>
+<Directory "/var/www/private/public">
     Allow from all
     Satisfy Any
 </Directory>
    
@@ -456,7 +457,6 @@ Satisfy Any
  • Require
    • 
-
 
    
 
    Available Languages:  en  |
diff --git a/docs/manual/mod/mod_access_compat.html.fr b/docs/manual/mod/mod_access_compat.html.fr
index b8ce55d420..4a729fd150 100644
--- a/docs/manual/mod/mod_access_compat.html.fr
+++ b/docs/manual/mod/mod_access_compat.html.fr
@@ -96,6 +96,7 @@ ce module sont devenues obsol
 
  • mod_authz_host
    • 
 
  • mod_authz_core
    • 
 
    
+
 
    top
    Directive Allow
    
 
    
 
     
 
 
 
 
 
    
@@ -480,7 +481,6 @@ Satisfy Any
  • Require
    • 
-
 
    
 
    Langues Disponibles:  en  |
diff --git a/docs/manual/mod/mod_access_compat.html.ja.utf8 b/docs/manual/mod/mod_access_compat.html.ja.utf8
index 1a9ba5cfa3..1b21dde70e 100644
--- a/docs/manual/mod/mod_access_compat.html.ja.utf8
+++ b/docs/manual/mod/mod_access_compat.html.ja.utf8
@@ -92,6 +92,7 @@
 
  • mod_authz_host
    • 
 
  • mod_authz_core
    • 
 
    
+
 
    top
    Allow ディレクティブ
    
 
    
 
 
 
 
 
    
@@ -441,7 +442,6 @@
 
  • Require
    • 
-
 
    
 
    翻訳済み言語:  en  |
diff --git a/docs/manual/mod/mod_access_compat.xml b/docs/manual/mod/mod_access_compat.xml
index d0acbc0587..390bef2380 100644
--- a/docs/manual/mod/mod_access_compat.xml
+++ b/docs/manual/mod/mod_access_compat.xml
@@ -198,7 +198,7 @@ Allow from 2001:db8::a00:20ff:fea7:ccea/10
 
     
 SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in
-<Directory /docroot>
+<Directory "/docroot">
     Order Deny,Allow
     Deny from all
     Allow from env=let_me_in
@@ -376,7 +376,7 @@ Deny from foo.example.org
     example,
    
 
     
-<Directory /www>
+<Directory "/www">
     Order Allow,Deny
 </Directory>
     
@@ -452,11 +452,11 @@ Satisfy Any
     
    
 
     
-<Directory /var/www/private>
+<Directory "/var/www/private">
     Require valid-user
 </Directory>
 
-<Directory /var/www/private/public>
+<Directory "/var/www/private/public">
     Allow from all
     Satisfy Any
 </Directory>
diff --git a/docs/manual/mod/mod_actions.html.de b/docs/manual/mod/mod_actions.html.de
index cf360ed5f1..75bf752204 100644
--- a/docs/manual/mod/mod_actions.html.de
+++ b/docs/manual/mod/mod_actions.html.de
@@ -57,6 +57,7 @@
 
  • Dynamische Inhalte mit CGI
    • 
 
  • Die Verwendung von Handlern
    • 
 
    
+
 
    top
    Action-Direktive
    
 
    
 
 
 
 
    
@@ -160,7 +161,6 @@
     
    
-
 
    
 
    Verfgbare Sprachen:  de  |
diff --git a/docs/manual/mod/mod_actions.html.en b/docs/manual/mod/mod_actions.html.en
index 0dffd02393..bc2504336a 100644
--- a/docs/manual/mod/mod_actions.html.en
+++ b/docs/manual/mod/mod_actions.html.en
@@ -53,6 +53,7 @@
 
  • Dynamic Content with CGI
    • 
 
  • Apache httpd's Handler Use
    • 
 
    
+
 
    top
    Action Directive
    
 
    
 
 
 
 
    
@@ -95,7 +96,7 @@ Action my-file-type /cgi-bin/program.cgi
     if you want to use the Action directive in
     virtual locations.
    
 
-    
    <Location /news>
+    
    <Location "/news">
     SetHandler news-handler
     Action news-handler /cgi-bin/news.cgi virtual
 </Location>
    
@@ -147,7 +148,6 @@ Script PUT /~bob/put.cgi
    
-
 
    
 
    Available Languages:  de  |
diff --git a/docs/manual/mod/mod_actions.html.fr b/docs/manual/mod/mod_actions.html.fr
index 6a489ce49c..7ef602376b 100644
--- a/docs/manual/mod/mod_actions.html.fr
+++ b/docs/manual/mod/mod_actions.html.fr
@@ -56,6 +56,7 @@ type de m
 
  • Utilisation des gestionnaires
 d'Apache httpd
    • 
 
    
+
 
    top
    Directive Action
    
 
    
 
 
 
 
 
    
@@ -157,7 +158,6 @@ Script PUT /~bob/put.cgi
-
 
    
 
    Langues Disponibles:  de  |
diff --git a/docs/manual/mod/mod_actions.html.ja.utf8 b/docs/manual/mod/mod_actions.html.ja.utf8
index a22b43485c..ba212c5a55 100644
--- a/docs/manual/mod/mod_actions.html.ja.utf8
+++ b/docs/manual/mod/mod_actions.html.ja.utf8
@@ -59,6 +59,7 @@ CGI スクリプトを実行する機能を提供
 
  • CGI による動的コンテンツ
    • 
 
  • Apache のハンドラの使用
    • 
 
    
+
 
    top
    Action ディレクティブ
    
 
    
 
 
 
 
 
    
@@ -168,7 +169,6 @@ Apache 2.1 で導入されました
    
-
 
    
 
    翻訳済み言語:  de  |
diff --git a/docs/manual/mod/mod_actions.html.ko.euc-kr b/docs/manual/mod/mod_actions.html.ko.euc-kr
index b3284ca2d7..a287e02122 100644
--- a/docs/manual/mod/mod_actions.html.ko.euc-kr
+++ b/docs/manual/mod/mod_actions.html.ko.euc-kr
@@ -56,6 +56,7 @@
 
  • CGI   
    • 
 
  • ġ ڵ鷯 
    • 
 
    
+
 
    top
    Action þ
    
 
    
     
 
 
 
 
    
@@ -157,7 +158,6 @@
     
    
-
 
    
 
     :  de  |
diff --git a/docs/manual/mod/mod_actions.xml b/docs/manual/mod/mod_actions.xml
index fc23f614a4..d9a9457ca3 100644
--- a/docs/manual/mod/mod_actions.xml
+++ b/docs/manual/mod/mod_actions.xml
@@ -99,7 +99,7 @@ Action my-file-type /cgi-bin/program.cgi
     virtual locations.
    
 
     
-<Location /news>
+<Location "/news">
     SetHandler news-handler
     Action news-handler /cgi-bin/news.cgi virtual
 </Location>
diff --git a/docs/manual/mod/mod_alias.html.en b/docs/manual/mod/mod_alias.html.en
index 5c6b4899ae..c18fe02199 100644
--- a/docs/manual/mod/mod_alias.html.en
+++ b/docs/manual/mod/mod_alias.html.en
@@ -86,6 +86,47 @@
 
  • Mapping URLs to the filesystem
    • 
 
    top
    
+
    
+
    Order of Processing
    
+
+    
    Aliases and Redirects occurring in different contexts are processed
+    like other directives according to standard merging rules.  But when multiple
+    Aliases or Redirects occur in the same context (for example, in the
+    same <VirtualHost>
+    section) they are processed in a particular order.
    
+
+    
    First, all Redirects are processed before Aliases are processed,
+    and therefore a request that matches a Redirect or RedirectMatch will never have Aliases
+    applied.  Second, the Aliases and Redirects are processed in the order
+    they appear in the configuration files, with the first match taking
+    precedence.
    
+
+    
    For this reason, when two or more of these directives apply to the
+    same sub-path, you must list the most specific path first in order for
+    all the directives to have an effect.  For example, the following
+    configuration will work as expected:
    
+
+    
    Alias /foo/bar /baz
+Alias /foo /gaq
    
+
+
+    
    But if the above two directives were reversed in order, the
+    /foo Alias
+    would always match before the /foo/bar Alias, so the latter directive would be
+    ignored.
    
+
+    
    When the Alias,
+    ScriptAlias and 
+    Redirect directives are used
+    within a <Location>
+    or <LocationMatch>
+    section, these directives will take precedence over any globally
+    defined Alias,
+    ScriptAlias and 
+    Redirect directives.
    
+
+
    
+
    top
    Alias Directive
    
 
    
 
 
 
 
 
    
@@ -138,7 +179,7 @@
     permit access to the target directory.
    Alias /image /ftp/pub/image
-<Directory /ftp/pub/image>
+<Directory "/ftp/pub/image">
     Require all granted
 </Directory>
    
 
@@ -152,10 +193,10 @@
     section the URL-path is omitted, and the file-path is interpreted
     using expression syntax.
    
 
-    
    <Location /image>
+    
    <Location "/image">
     Alias /ftp/pub/image
 </Location>
-<LocationMatch /error/(?<NUMBER>[0-9]+)>
+<LocationMatch "/error/(?<NUMBER>[0-9]+)">
     Alias /usr/local/apache/errors/%{env:MATCH_NUMBER}.html
 </LocationMatch>
    
 
@@ -349,13 +390,13 @@ Redirect 303 /three http://example.com/other
    
     section with the URL-path omitted, then the URL parameter will be
     interpreted using expression syntax.
    
 
-    
    <Location /one>
+    
    <Location "/one">
     Redirect permanent http://example.com/two
 </Location>
    
-<Location /three>
+<Location "/three">
     Redirect 303 http://example.com/other
 </Location>
    
-<LocationMatch /error/(?<NUMBER>[0-9]+)>
+<LocationMatch "/error/(?<NUMBER>[0-9]+)">
     Redirect permanent http://example.com/errors/%{env:MATCH_NUMBER}.html
 </LocationMatch>
    
     
    
@@ -457,7 +498,7 @@ target as a CGI script
     server to run the script /web/cgi-bin/foo.  This configuration
     is essentially equivalent to:
    
     
    Alias /cgi-bin/ /web/cgi-bin/
-<Location /cgi-bin >
+<Location "/cgi-bin" >
     SetHandler cgi-script
     Options +ExecCGI
 </Location>
    
@@ -483,7 +524,7 @@ target as a CGI script
     choose to place your CGI scripts in a directory already
     accessible from the web, do not use
     ScriptAlias.  Instead, use <Directory>, SetHandler, and Options as in:
-    
    <Directory /usr/local/apache2/htdocs/cgi-bin >
+    
    <Directory "/usr/local/apache2/htdocs/cgi-bin">
     SetHandler cgi-script
     Options ExecCGI
 </Directory>
    
@@ -500,10 +541,10 @@ target as a CGI script
     section with the URL-path omitted, then the URL parameter will be
     interpreted using expression syntax.
    
 
-    
    <Location /cgi-bin >
+    
    <Location "/cgi-bin">
     ScriptAlias /web/cgi-bin/
 </Location>
-<LocationMatch /cgi-bin/errors/(?<NUMBER>[0-9]+)>
+<LocationMatch "/cgi-bin/errors/(?<NUMBER>[0-9]+)">
     ScriptAlias /web/cgi-bin/errors/%{env:MATCH_NUMBER}.cgi
 </LocationMatch>
    
     
    
@@ -556,47 +597,6 @@ and designates the target as a CGI script
     details.
    
 
 
-
-
    top
    
-
    
-
    Order of Processing
    
-
-    
    Aliases and Redirects occurring in different contexts are processed
-    like other directives according to standard merging rules.  But when multiple
-    Aliases or Redirects occur in the same context (for example, in the
-    same <VirtualHost>
-    section) they are processed in a particular order.
    
-
-    
    First, all Redirects are processed before Aliases are processed,
-    and therefore a request that matches a Redirect or RedirectMatch will never have Aliases
-    applied.  Second, the Aliases and Redirects are processed in the order
-    they appear in the configuration files, with the first match taking
-    precedence.
    
-
-    
    For this reason, when two or more of these directives apply to the
-    same sub-path, you must list the most specific path first in order for
-    all the directives to have an effect.  For example, the following
-    configuration will work as expected:
    
-
-    
    Alias /foo/bar /baz
-Alias /foo /gaq
    
-
-
-    
    But if the above two directives were reversed in order, the
-    /foo Alias
-    would always match before the /foo/bar Alias, so the latter directive would be
-    ignored.
    
-
-    
    When the Alias,
-    ScriptAlias and 
-    Redirect directives are used
-    within a <Location>
-    or <LocationMatch>
-    section, these directives will take precedence over any globally
-    defined Alias,
-    ScriptAlias and 
-    Redirect directives.
    
-
 
    
 
 
    
diff --git a/docs/manual/mod/mod_alias.html.fr b/docs/manual/mod/mod_alias.html.fr
index eb8fc64099..da042c04cc 100644
--- a/docs/manual/mod/mod_alias.html.fr
+++ b/docs/manual/mod/mod_alias.html.fr
@@ -68,7 +68,10 @@ redirection d'URL
     plutt les outils fournis par le module mod_rewrite
    
 
 
    
-
    Directives
    
+
 
    top
    
+
    
+
    Chronologie du traitement
    
+
+    
    Les alias et redirections apparaissant dans diffrents contextes
+    sont traits comme les autres directives en respectant les rgles de fusion standards. Par
+    contre, ils sont traits selon une chronologie particulire
+    lorsqu'ils apparaissent dans le mme contexte (par exemple, dans la
+    mme section <VirtualHost>).
    
+
+    
    Premirement, toutes les redirections sont traites avant les
+    alias, et ainsi, une requte qui correspond  une directive
+    Redirect ou RedirectMatch ne se verra jamais
+    appliquer d'alias. Deuximement, les alias et redirections sont
+    traits selon l'ordre dans lequel ils apparaissent dans le fichier
+    de configuration, seule la premire correspondance tant prise en
+    compte.
    
+
+    
    Ainsi, lorsqu'une ou plusieurs de ces directives s'appliquent au
+    mme sous-rpertoire, vous devez classer les chemins du plus prcis
+    au moins prcis afin que toutes les directives puissent
+    ventuellement s'appliquer, comme dans l'exemple suivant :
    
+
+    
    Alias /foo/bar /baz
+Alias /foo /gaq
    
+
+
+    
    Si l'ordre des directives tait invers, la directive Alias ayant pour argument
+    /foo serait toujours applique avant la directive
+    Alias ayant pour argument
+    /foo/bar, et cette dernire serait toujours
+    ignore.
    
+
+    
    La dfinition de directives Alias, ScriptAlias ou Redirect au sein de sections
+    <Location> ou
+    <LocationMatch>
+    l'emporte sur d'autres dfinitions ventuelles de ces mmes
+    directives au niveau de la configuration gnrale du serveur.
    
+
+
    
+
    top
    
 
    Directive Alias
    
 
    
 
    Description:Maps URLs to filesystem locations
    
 
     
    
     dtails.
    
 
 
-
-
    top
    
-
    
-
    Chronologie du traitement
    
-
-    
    Les alias et redirections apparaissant dans diffrents contextes
-    sont traits comme les autres directives en respectant les rgles de fusion standards. Par
-    contre, ils sont traits selon une chronologie particulire
-    lorsqu'ils apparaissent dans le mme contexte (par exemple, dans la
-    mme section <VirtualHost>).
    
-
-    
    Premirement, toutes les redirections sont traites avant les
-    alias, et ainsi, une requte qui correspond  une directive
-    Redirect ou RedirectMatch ne se verra jamais
-    appliquer d'alias. Deuximement, les alias et redirections sont
-    traits selon l'ordre dans lequel ils apparaissent dans le fichier
-    de configuration, seule la premire correspondance tant prise en
-    compte.
    
-
-    
    Ainsi, lorsqu'une ou plusieurs de ces directives s'appliquent au
-    mme sous-rpertoire, vous devez classer les chemins du plus prcis
-    au moins prcis afin que toutes les directives puissent
-    ventuellement s'appliquer, comme dans l'exemple suivant :
    
-
-    
    Alias /foo/bar /baz
-Alias /foo /gaq
    
-
-
-    
    Si l'ordre des directives tait invers, la directive Alias ayant pour argument
-    /foo serait toujours applique avant la directive
-    Alias ayant pour argument
-    /foo/bar, et cette dernire serait toujours
-    ignore.
    
-
-    
    La dfinition de directives Alias, ScriptAlias ou Redirect au sein de sections
-    <Location> ou
-    <LocationMatch>
-    l'emporte sur d'autres dfinitions ventuelles de ces mmes
-    directives au niveau de la configuration gnrale du serveur.
    
-
 
    
diff --git a/docs/manual/mod/mod_alias.html.ja.utf8 b/docs/manual/mod/mod_alias.html.ja.utf8
index 44129cbc44..eee433c765 100644
--- a/docs/manual/mod/mod_alias.html.ja.utf8
+++ b/docs/manual/mod/mod_alias.html.ja.utf8
@@ -64,7 +64,10 @@
     で提供されるツールを使用してください。
    
 
 
    
-
    ディレクティブ
    
+
 
    top
    
+
    
+
    処理の順番
    
+
+
    様々なコンテキスト中での Alias や Redirect は他のディレクティブと
+同じように標準の マージ規則 に
+従って処理されます。ただし、(例えば <VirtualHost> セクションの中のように) 複数の Alias や Redirect が
+同じコンテキスト中に現れた場合は決まった順番で処理されます。
    
+
+
    まず、Alias の前にすべての Redirect が処理されます。ですから、Redirect か RedirectMatch にマッチするリクエストには
+Alias は決して適用されません。次に、Alias と Redirect が設定ファイル中の
+順番に適用され、最初にマッチしたものが優先されます。
    
+
+
    ですから、二つ以上のディレクティブが同じパスに適用されるときは、
+すべてのディレクティブの効果を得るためにはより詳しいパスを先に書く
+必要があります。例えば、次の設定は期待通りの動作をします:
    
+
+
    
+Alias /foo/bar /baz
    
+Alias /foo /gaq
+
    
+
+
    しかし、上記の二つのディレクティブの順番が逆になると、
+/foo Alias が
+常に /foo/bar Alias より先にマッチしますので、後者は
+決して適用されることはありません。
    
+
+
    
+
    top
    
 
    Alias ディレクティブ
    
 
    
 
    Description:Met en correspondance des URLs avec des chemins du systme
@@ -567,46 +607,6 @@ comme un script CGI
    
 
 
    
@@ -354,34 +382,6 @@ CGI スクリプトに指定
       ScriptAliasMatch ^/cgi-bin(.*) /usr/local/apache/cgi-bin$1
     
    
 
-
-
    top
    
-
    
-
    処理の順番
    
-
-
    様々なコンテキスト中での Alias や Redirect は他のディレクティブと
-同じように標準の マージ規則 に
-従って処理されます。ただし、(例えば <VirtualHost> セクションの中のように) 複数の Alias や Redirect が
-同じコンテキスト中に現れた場合は決まった順番で処理されます。
    
-
-
    まず、Alias の前にすべての Redirect が処理されます。ですから、Redirect か RedirectMatch にマッチするリクエストには
-Alias は決して適用されません。次に、Alias と Redirect が設定ファイル中の
-順番に適用され、最初にマッチしたものが優先されます。
    
-
-
    ですから、二つ以上のディレクティブが同じパスに適用されるときは、
-すべてのディレクティブの効果を得るためにはより詳しいパスを先に書く
-必要があります。例えば、次の設定は期待通りの動作をします:
    
-
-
    
-Alias /foo/bar /baz
    
-Alias /foo /gaq
-
    
-
-
    しかし、上記の二つのディレクティブの順番が逆になると、
-/foo Alias が
-常に /foo/bar Alias より先にマッチしますので、後者は
-決して適用されることはありません。
    
-
 
    
diff --git a/docs/manual/mod/mod_alias.html.ko.euc-kr b/docs/manual/mod/mod_alias.html.ko.euc-kr
index db6fb49c06..b98b4e9d21 100644
--- a/docs/manual/mod/mod_alias.html.ko.euc-kr
+++ b/docs/manual/mod/mod_alias.html.ko.euc-kr
@@ -54,7 +54,10 @@
     mod_rewrite ϴ  ̿϶.
    
 
 
    
-
    þ
    
+
 
    top
    
+
    
+
    ó 
    
+
+
     ٸ ҿ Alias Redirect ϸ ٸ þ
+ ǥ  
+ óѴ. ׷  ҿ ( ,  <VirtualHost> ǿ)
+Alias Redirect ϸ Ʒ  óѴ.
    
+
+
      Redirect ó  Alias óѴ. ׷
+Redirect RedirectMatch شϴ û
+ Alias ʴ´. ׸ Alias Redirect Ͽ
+ù°   Ѵ.
    
+
+
    ׷  þ  ο شϴ  
+þ ϱؼ   θ  ؾ Ѵ.
+ ,   ǵѴ Ѵ:
    
+
+
    
+Alias /foo/bar /baz
    
+Alias /foo /gaq
+
    
+
+
    ׷   þ  ٲٸ /foo/bar
+Alias 
+/foo Alias
+ϹǷ ׻ ι° þ Ѵ.
    
+
+
    
+
    top
    
 
    Alias þ
    
 
    
 
    説明:URL をファイルシステムの位置にマップする
    
 
 
    
@@ -320,35 +349,6 @@
       ScriptAliasMatch ^/cgi-bin(.*) /usr/local/apache/cgi-bin$1
     
    
 
-
-
    top
    
-
    
-
    ó 
    
-
-
     ٸ ҿ Alias Redirect ϸ ٸ þ
- ǥ  
- óѴ. ׷  ҿ ( ,  <VirtualHost> ǿ)
-Alias Redirect ϸ Ʒ  óѴ.
    
-
-
      Redirect ó  Alias óѴ. ׷
-Redirect RedirectMatch شϴ û
- Alias ʴ´. ׸ Alias Redirect Ͽ
-ù°   Ѵ.
    
-
-
    ׷  þ  ο شϴ  
-þ ϱؼ   θ  ؾ Ѵ.
- ,   ǵѴ Ѵ:
    
-
-
    
-Alias /foo/bar /baz
    
-Alias /foo /gaq
-
    
-
-
    ׷   þ  ٲٸ /foo/bar
-Alias 
-/foo Alias
-ϹǷ ׻ ι° þ Ѵ.
    
-
 
    
diff --git a/docs/manual/mod/mod_alias.html.tr.utf8 b/docs/manual/mod/mod_alias.html.tr.utf8
index d6e65c8b44..636de7e1f1 100644
--- a/docs/manual/mod/mod_alias.html.tr.utf8
+++ b/docs/manual/mod/mod_alias.html.tr.utf8
@@ -55,7 +55,10 @@ eşlenmesini sağlar ve URL yönlendirmesi yapar.
       sağlanan araçlar kullanılır.
    
 
   
    
-
    Yönergeler
    
+
    Konular
    
+
    Yönergeler
    
 
-
    Konular
    
-
    Ayrıca bakınız:
    
+
    Ayrıca bakınız:
    
 
    
 
    top
    
+
    
+
    İşlem Sırası
    
+
+    
    Farklı bağlamlarda bulunan Alias ve Redirect
+      yönergeleri standart katıştırma
+      kuralları ile ilgili diğer yönergeler gibi işleme sokulur. Fakat
+      aynı bağlam dahilinde (örneğin, aynı <VirtualHost> bölümünde) çok fazla Alias ve Redirect varsa bunlar belli bir
+      sıraya göre işleme sokulurlar.
    
+
+    
    İlk adımda, Alias’lardan önce
+      bütün Redirect yönergeleri
+      işleme sokulur. Bu bakımdan bir Redirect veya RedirectMatch ile eşleşen bir istek için
+      hiçbir Alias
+      uygulanmayacaktır. İkinci adımda yapılandırma dosyasında yer aldıkları
+      sıraya göre Redirect ve
+      Alias yönergeleri işleme
+      sokulurlar, dolayısıyla ilk eşleşme öncelikli olmuş olur.
    
+
+    
    İlk eşleşmenin öncelikli olması sebebiyle, bu yönergelerin birden
+      fazlası aynı alt yola uygulandığı takdirde, tüm yönergelerin etkili
+      olabilmesi için en uzun yolu sıralamada en öne almalısınız. Örneğin
+      aşağıdaki yapılandırma beklendiği gibi çalışacaktır:
    
+
+    
    
+    Alias /foo/bar /baz
    
+    Alias /foo /gaz
+    
    
+
+    
    Ama yukarıdaki iki satır ters sırada yerleştirilmiş olsaydı,
+      /foo rumuzu  daima /foo/bar rumuzundan önce
+      eşleşecek, dolayısıyla ikinci yönerge yok sayılacaktı.
    
+
+  
    
+
    top
    
 
    Alias Yönergesi
    
 
    
 
    :URL Ư Ͻý ҷ Ѵ
    
 
 
    
@@ -493,40 +527,6 @@ eşler ve hedefi bir CGI betiği olarak çalıştırır.
-
    top
    
-
    
-
    İşlem Sırası
    
-
-    
    Farklı bağlamlarda bulunan Alias ve Redirect
-      yönergeleri standart katıştırma
-      kuralları ile ilgili diğer yönergeler gibi işleme sokulur. Fakat
-      aynı bağlam dahilinde (örneğin, aynı <VirtualHost> bölümünde) çok fazla Alias ve Redirect varsa bunlar belli bir
-      sıraya göre işleme sokulurlar.
    
-
-    
    İlk adımda, Alias’lardan önce
-      bütün Redirect yönergeleri
-      işleme sokulur. Bu bakımdan bir Redirect veya RedirectMatch ile eşleşen bir istek için
-      hiçbir Alias
-      uygulanmayacaktır. İkinci adımda yapılandırma dosyasında yer aldıkları
-      sıraya göre Redirect ve
-      Alias yönergeleri işleme
-      sokulurlar, dolayısıyla ilk eşleşme öncelikli olmuş olur.
    
-
-    
    İlk eşleşmenin öncelikli olması sebebiyle, bu yönergelerin birden
-      fazlası aynı alt yola uygulandığı takdirde, tüm yönergelerin etkili
-      olabilmesi için en uzun yolu sıralamada en öne almalısınız. Örneğin
-      aşağıdaki yapılandırma beklendiği gibi çalışacaktır:
    
-
-    
    
-    Alias /foo/bar /baz
    
-    Alias /foo /gaz
-    
    
-
-    
    Ama yukarıdaki iki satır ters sırada yerleştirilmiş olsaydı,
-      /foo rumuzu  daima /foo/bar rumuzundan önce
-      eşleşecek, dolayısıyla ikinci yönerge yok sayılacaktı.
    
-
-  
    
 
    Mevcut Diller:  en  |
diff --git a/docs/manual/mod/mod_alias.xml b/docs/manual/mod/mod_alias.xml
index b4e2711c04..d6572d4395 100644
--- a/docs/manual/mod/mod_alias.xml
+++ b/docs/manual/mod/mod_alias.xml
@@ -170,7 +170,7 @@ Alias /foo /gaq
 
     
 Alias /image /ftp/pub/image
-<Directory /ftp/pub/image>
+<Directory "/ftp/pub/image">
     Require all granted
 </Directory>
     
@@ -185,10 +185,10 @@ Alias /image /ftp/pub/image
     using expression syntax.
    
 
     
-<Location /image>
+<Location "/image">
     Alias /ftp/pub/image
 </Location>
-<LocationMatch /error/(?<NUMBER>[0-9]+)>
+<LocationMatch "/error/(?<NUMBER>[0-9]+)">
     Alias /usr/local/apache/errors/%{env:MATCH_NUMBER}.html
 </LocationMatch>
     
@@ -393,13 +393,13 @@ Redirect 303 /three http://example.com/other
     interpreted using expression syntax.
    
 
     
-<Location /one>
+<Location "/one">
     Redirect permanent http://example.com/two
 </Location>
    
-<Location /three>
+<Location "/three">
     Redirect 303 http://example.com/other
 </Location>
    
-<LocationMatch /error/(?<NUMBER>[0-9]+)>
+<LocationMatch "/error/(?<NUMBER>[0-9]+)">
     Redirect permanent http://example.com/errors/%{env:MATCH_NUMBER}.html
 </LocationMatch>
    
         
@@ -506,7 +506,7 @@ target as a CGI script
     is essentially equivalent to:
    
     
 Alias /cgi-bin/ /web/cgi-bin/
-<Location /cgi-bin >
+<Location "/cgi-bin" >
     SetHandler cgi-script
     Options +ExecCGI
 </Location>
@@ -537,7 +537,7 @@ Alias /cgi-bin/ /web/cgi-bin/
     module="core">SetHandler, and Options as in:
     
-<Directory /usr/local/apache2/htdocs/cgi-bin >
+<Directory "/usr/local/apache2/htdocs/cgi-bin">
     SetHandler cgi-script
     Options ExecCGI
 </Directory>
@@ -555,10 +555,10 @@ Alias /cgi-bin/ /web/cgi-bin/
     interpreted using expression syntax.
    
 
     
-<Location /cgi-bin >
+<Location "/cgi-bin">
     ScriptAlias /web/cgi-bin/
 </Location>
-<LocationMatch /cgi-bin/errors/(?<NUMBER>[0-9]+)>
+<LocationMatch "/cgi-bin/errors/(?<NUMBER>[0-9]+)">
     ScriptAlias /web/cgi-bin/errors/%{env:MATCH_NUMBER}.cgi
 </LocationMatch>
    
         
diff --git a/docs/manual/mod/mod_allowhandlers.html.en b/docs/manual/mod/mod_allowhandlers.html.en
index e770dca70d..855227eb01 100644
--- a/docs/manual/mod/mod_allowhandlers.html.en
+++ b/docs/manual/mod/mod_allowhandlers.html.en
@@ -35,7 +35,7 @@
 
    This module makes it easy to restrict which handlers may be used for a
 request. A possible configuration would be:
    
 
-
    <Location />
+
    <Location "/">
   AllowHandlers not server-info server-status balancer-manager ldap-status
 </Location>
    
 
@@ -54,6 +54,7 @@ returns 403 FORBIDDEN to the client. This can be used with directives like
 
  • SetHandler
    • 
 
  • AddHandler
    • 
 
    
+
 
    top
    AllowHandlers Directive
    
 
    
 
    Açıklama:URL’leri dosya sistemi konumlarıyla eşler.
    
 
 
 
 
 
 
    
@@ -72,7 +73,7 @@ set. The special vallue all can be used to allow all
 handlers again in a later config section, even if some headers were denied
 earlier in the configuration merge order:
    
 
-
    <Location /server-status>
+
    <Location "/server-status">
   AllowHandlers all
   SetHandler server-status
 </Location>
    
@@ -80,7 +81,6 @@ earlier in the configuration merge order:
    
 
 
 
-
 
 
    
 
    Available Languages:  en 
    
diff --git a/docs/manual/mod/mod_allowhandlers.xml b/docs/manual/mod/mod_allowhandlers.xml
index 2dcd165af5..aa4d16ccc1 100644
--- a/docs/manual/mod/mod_allowhandlers.xml
+++ b/docs/manual/mod/mod_allowhandlers.xml
@@ -33,7 +33,7 @@
 request. A possible configuration would be:
    
 
 
-<Location />
+<Location "/">
   AllowHandlers not server-info server-status balancer-manager ldap-status
 </Location>
 
@@ -65,7 +65,7 @@ handlers again in a later config section, even if some headers were denied
 earlier in the configuration merge order:
    
 
 
-<Location /server-status>
+<Location "/server-status">
   AllowHandlers all
   SetHandler server-status
 </Location>
diff --git a/docs/manual/mod/mod_allowmethods.html.en b/docs/manual/mod/mod_allowmethods.html.en
index b5eb35cdda..f3c0459586 100644
--- a/docs/manual/mod/mod_allowmethods.html.en
+++ b/docs/manual/mod/mod_allowmethods.html.en
@@ -36,7 +36,7 @@
 
    This module makes it easy to restrict what HTTP methods can
 used on an server. The most common configuration would be:
    
 
-
    <Location />
+
    <Location "/">
    AllowMethods GET POST OPTIONS
 </Location>
    
 
@@ -47,6 +47,7 @@ used on an server. The most common configuration would be:
    
 
  •  AllowMethods
    • 
 
 
    
+
 
    top
    
 
    AllowMethods Directive
    
 
    
@@ -64,7 +65,7 @@ RFC given in upper case. The GET and HEAD methods are treated as
 equivalent. The reset keyword can be used
 turn off mod_allowmethods in a deeper nested context:
    
 
-
    <Location /svn>
+
    <Location "/svn">
    AllowMethods reset
 </Location>
    
 
@@ -79,7 +80,6 @@ kludgy implementation of LimitExcept.
    
 
 
-
 
 
    
 
    Available Languages:  en  |
diff --git a/docs/manual/mod/mod_allowmethods.html.fr b/docs/manual/mod/mod_allowmethods.html.fr
index 21bdb70d0c..bc50398c72 100644
--- a/docs/manual/mod/mod_allowmethods.html.fr
+++ b/docs/manual/mod/mod_allowmethods.html.fr
@@ -48,6 +48,7 @@ est du style :
    
 
  •  AllowMethods
    • 
 
 
    
+
 
    top
    
 
    Directive AllowMethods
    
 
    
@@ -81,7 +82,6 @@ d'imbrication :
    
 remplacer l'implmentation "bricole" des directives Limit et LimitExcept.
    
-
 
    
 
    Langues Disponibles:  en  |
diff --git a/docs/manual/mod/mod_allowmethods.xml b/docs/manual/mod/mod_allowmethods.xml
index d743b657c3..3fe9a00276 100644
--- a/docs/manual/mod/mod_allowmethods.xml
+++ b/docs/manual/mod/mod_allowmethods.xml
@@ -43,7 +43,7 @@ in order for it to rebuild correctly.
 used on an server. The most common configuration would be:
    
 
 
-<Location />
+<Location "/">
    AllowMethods GET POST OPTIONS
 </Location>
 
@@ -67,7 +67,7 @@ equivalent. The reset keyword can be used
 turn off mod_allowmethods in a deeper nested context:
    
 
 
-<Location /svn>
+<Location "/svn">
    AllowMethods reset
 </Location>
 
diff --git a/docs/manual/mod/mod_asis.html.fr b/docs/manual/mod/mod_asis.html.fr
index 1f5b596479..4251b5e992 100644
--- a/docs/manual/mod/mod_asis.html.fr
+++ b/docs/manual/mod/mod_asis.html.fr
@@ -47,12 +47,12 @@ HTTP
     
    Pour des raisons historiques, ce module traitera aussi tout
     fichier dont le type MIME est httpd/send-as-is.
    
 
    
-
    Directives
    
-
    Ce module ne fournit aucune directive.
    
-
    Sujets
    
+
    Sujets
    
 
    Voir aussi
    
+
    Directives
    
+
    Ce module ne fournit aucune directive.
    
+
    Voir aussi
    
 
      
 
    • mod_headers
      • 
 
    • mod_cern_meta
      • 
diff --git a/docs/manual/mod/mod_asis.html.ja.utf8 b/docs/manual/mod/mod_asis.html.ja.utf8
index 1af9c46ad5..b56bc62883 100644
--- a/docs/manual/mod/mod_asis.html.ja.utf8
+++ b/docs/manual/mod/mod_asis.html.ja.utf8
@@ -50,12 +50,12 @@
     
      歴史的な理由により、このモジュールは mime タイプ
     httpd/send-as-is のファイルも処理します。
      
 
    
-
    ディレクティブ
    
-
    このモジュールにディレクティブはありません。
    
-
    トピック
    
+
    トピック
    
 
    参照
    
+
    ディレクティブ
    
+
    このモジュールにディレクティブはありません。
    
+
    参照
    
 
      
 
    • mod_headers
      • 
 
    • mod_cern_meta
      • 
diff --git a/docs/manual/mod/mod_asis.html.ko.euc-kr b/docs/manual/mod/mod_asis.html.ko.euc-kr
index f2de124cc6..86ba6a51bc 100644
--- a/docs/manual/mod/mod_asis.html.ko.euc-kr
+++ b/docs/manual/mod/mod_asis.html.ko.euc-kr
@@ -48,12 +48,12 @@
     
      ſ   mime type httpd/send-as-is
     ϵ óߴ.
      
 
    
-
    þ
    
-
     ⿡ þ ϴ.
    
-
    
+
    
 
      
 
    •  
      • 
-
    
+
    þ
    
+
     ⿡ þ ϴ.
    
+
    
 
      
 
    • mod_headers
      • 
 
    • mod_cern_meta
      • 
diff --git a/docs/manual/mod/mod_auth_basic.html.en b/docs/manual/mod/mod_auth_basic.html.en
index d4885e8434..0e78f816d6 100644
--- a/docs/manual/mod/mod_auth_basic.html.en
+++ b/docs/manual/mod/mod_auth_basic.html.en
@@ -57,6 +57,7 @@
 
    • Require
      • 
 
    • Authentication howto
      • 
 
    
+
 
    top
    
 
    AuthBasicAuthoritative Directive
    
 
    
 
 
 
    
@@ -251,7 +252,6 @@ Digest Authentication was in force instead of Basic Authentication.
     
-
 
    
 
    Available Languages:  en  |
diff --git a/docs/manual/mod/mod_auth_basic.html.fr b/docs/manual/mod/mod_auth_basic.html.fr
index 92c5cbd031..c2aa3f9a64 100644
--- a/docs/manual/mod/mod_auth_basic.html.fr
+++ b/docs/manual/mod/mod_auth_basic.html.fr
@@ -61,6 +61,7 @@
 
  • Mode d'emploi de
 l'authentification
    • 
 
    
+
 
    top
    Directive AuthBasicAuthoritative
    
 
    
 
 
 
 
    
@@ -280,7 +281,6 @@ Apache
       refuser l'accs.
-
 
    
 
    Langues Disponibles:  en  |
diff --git a/docs/manual/mod/mod_auth_basic.html.ja.utf8 b/docs/manual/mod/mod_auth_basic.html.ja.utf8
index a8934c7c47..9f55380602 100644
--- a/docs/manual/mod/mod_auth_basic.html.ja.utf8
+++ b/docs/manual/mod/mod_auth_basic.html.ja.utf8
@@ -66,6 +66,7 @@
 
  • <SatisfyOne>
    • 
 
  • Authentication howto
    • 
 
    
+
 
    top
    AuthBasicAuthoritative ディレクティブ
    
 
    
 
 
 
 
    
@@ -162,7 +163,6 @@ Digest Authentication was in force instead of Basic Authentication.
 
    このディレクティブの解説文書は
             まだ翻訳されていません。英語版をご覧ください。
             
    
-
 
 
    
 
    翻訳済み言語:  en  |
diff --git a/docs/manual/mod/mod_auth_basic.html.ko.euc-kr b/docs/manual/mod/mod_auth_basic.html.ko.euc-kr
index 5860430e82..6edd089b4e 100644
--- a/docs/manual/mod/mod_auth_basic.html.ko.euc-kr
+++ b/docs/manual/mod/mod_auth_basic.html.ko.euc-kr
@@ -55,6 +55,7 @@
 
  • AuthName
    • 
 
  • AuthType
    • 
 
    
+
 
    top
    
 
    AuthBasicAuthoritative þ
    
 
@@ -155,7 +156,6 @@ Digest Authentication was in force instead of Basic Authentication.
 
    The documentation for this directive has
             not been translated yet. Please have a look at the English
             version.
    
-
 
 
    
 
     :  en  |
diff --git a/docs/manual/mod/mod_auth_digest.html.en b/docs/manual/mod/mod_auth_digest.html.en
index 7e1a8cead4..6d5a605beb 100644
--- a/docs/manual/mod/mod_auth_digest.html.en
+++ b/docs/manual/mod/mod_auth_digest.html.en
@@ -68,6 +68,48 @@
 
  • Authentication howto
    • 
 
    
 
    top
    
+
    
+
    Using Digest Authentication
    
+
+    
    To use MD5 Digest authentication, simply
+    change the normal AuthType Basic and
+    AuthBasicProvider
+    to AuthType Digest and
+    AuthDigestProvider,
+    when setting up authentication, then add a
+    AuthDigestDomain directive containing at least the root
+    URI(s) for this protection space.
    
+
+    
    Appropriate user (text) files can be created using the
+    htdigest tool.
    
+
+    
    Example:
    <Location "/private/">
+    AuthType Digest
+    AuthName "private area"
+    AuthDigestDomain "/private/" "http://mirror.my.dom/private2/"
+    
+    AuthDigestProvider file
+    AuthUserFile "/web/auth/.digest_pw"
+    Require valid-user
+</Location>
    
+
    
+
+    
    Note
    
+    
    Digest authentication was intended to be more secure than basic
+    authentication, but no longer fulfills that design goal. A
+    man-in-the-middle attacker can trivially force the browser to downgrade
+    to basic authentication. And even a passive eavesdropper can brute-force
+    the password using today's graphics hardware, because the hashing
+    algorithm used by digest authentication is too fast. Another problem is
+    that the storage of the passwords on the server is insecure. The contents
+    of a stolen htdigest file can be used directly for digest authentication.
+    Therefore using mod_ssl to encrypt the whole connection is
+    strongly recommended.
    
+    
    mod_auth_digest only works properly on platforms
+      where APR supports shared memory.
    
+    
    
+
    
+
    top
    
 
    AuthDigestAlgorithm Directive
    
 
     via mod_ssl constitue une bien meilleure
     alternative.
    
-
    Directives
    
+
    Sujets
    
+
    Directives
    
 
-
    Sujets
    
-
    Voir aussi
    
+
    Voir aussi
    
 
    
 
    top
    
+
    
+
    Utilisation de l'authentification  base de
+condenss
    
+
+    
    Pour utiliser l'authentification  base de condenss MD5, vous
+    devez simplement remplacer AuthType Basic et AuthBasicProvider respectivement
+    par AuthType Digest et AuthDigestProvider lorsque vous
+    configurez l'authentification, puis ajouter une directive AuthDigestDomain contenant au
+    moins la(les) URI(s) racine(s) de la zone  protger.
    
+
+    
    On peut crer les fichiers utilisateur appropris (au format
+    texte)  l'aide de l'outil htdigest.
    
+
+    
    Exemple :
    <Location /private/>
+    AuthType Digest
+    AuthName "private area"
+    AuthDigestDomain /private/ http://mirror.my.dom/private2/
+    
+    AuthDigestProvider file
+    AuthUserFile /web/auth/.digest_pw
+    Require valid-user
+</Location>
    
+
    
+
+    
    Note
    
+    
    L'authentification  base de condens a t conue pour amliorer
+    la scurit par rapport  l'authentification basique, mais il
+    s'avre que ce but n'a pas t atteint. Un attaquant de type
+    "man-in-the-middle" peut facilement forcer le navigateur  revenir 
+    une authentification basique. Mme une oreille indiscrte passive
+    peut retrouver le mot de passe par force brute avec les moyens
+    modernes, car l'algorithme de hashage utilis par l'authentification
+     base de condens est trop rapide. Autre problme, le stockage des
+    mots de passe sur le serveur n'est pas sr. Le contenu d'un fichier
+    htdigest vol peut tre utilis directement pour l'authentification
+     base de condens. Il est donc fortement recommand d'utiliser
+    mod_ssl pour chiffrer la connexion.
    
+    
    mod_auth_digest ne fonctionne correctement que
+    sur les plates-formes o APR supporte la mmoire partage.
    
+    
    
+
    
+
    top
    
 
    Directive AuthDigestAlgorithm
    
 
    
 
    Description:Selects the algorithm used to calculate the challenge and
@@ -256,48 +298,6 @@ AuthDigestShmemSize 1024K
 AuthDigestShmemSize 1M
 
 
-
-
    top
    
-
    
-
    Using Digest Authentication
    
-
-    
    To use MD5 Digest authentication, simply
-    change the normal AuthType Basic and
-    AuthBasicProvider
-    to AuthType Digest and
-    AuthDigestProvider,
-    when setting up authentication, then add a
-    AuthDigestDomain directive containing at least the root
-    URI(s) for this protection space.
    
-
-    
    Appropriate user (text) files can be created using the
-    htdigest tool.
    
-
-    
    Example:
    <Location "/private/">
-    AuthType Digest
-    AuthName "private area"
-    AuthDigestDomain "/private/" "http://mirror.my.dom/private2/"
-    
-    AuthDigestProvider file
-    AuthUserFile "/web/auth/.digest_pw"
-    Require valid-user
-</Location>
    
-
    
-
-    
    Note
    
-    
    Digest authentication was intended to be more secure than basic
-    authentication, but no longer fulfills that design goal. A
-    man-in-the-middle attacker can trivially force the browser to downgrade
-    to basic authentication. And even a passive eavesdropper can brute-force
-    the password using today's graphics hardware, because the hashing
-    algorithm used by digest authentication is too fast. Another problem is
-    that the storage of the passwords on the server is insecure. The contents
-    of a stolen htdigest file can be used directly for digest authentication.
-    Therefore using mod_ssl to encrypt the whole connection is
-    strongly recommended.
    
-    
    mod_auth_digest only works properly on platforms
-      where APR supports shared memory.
    
-    
    
 
    
 
 
    
diff --git a/docs/manual/mod/mod_auth_digest.html.fr b/docs/manual/mod/mod_auth_digest.html.fr
index 7354f919c1..ec7e2221d5 100644
--- a/docs/manual/mod/mod_auth_digest.html.fr
+++ b/docs/manual/mod/mod_auth_digest.html.fr
@@ -50,7 +50,11 @@ MD5
    
 
    
     invoqu en affectant la valeur ldap  la directive
     AuthBasicProvider.
    
-
    
 
    Description:Slectionne l'algorithme utilis pour calculer les
@@ -278,48 +320,6 @@ AuthDigestShmemSize 1024K
 AuthDigestShmemSize 1M
 
 
-
-
    top
    
-
    
-
    Utilisation de l'authentification  base de
-condenss
    
-
-    
    Pour utiliser l'authentification  base de condenss MD5, vous
-    devez simplement remplacer AuthType Basic et AuthBasicProvider respectivement
-    par AuthType Digest et AuthDigestProvider lorsque vous
-    configurez l'authentification, puis ajouter une directive AuthDigestDomain contenant au
-    moins la(les) URI(s) racine(s) de la zone  protger.
    
-
-    
    On peut crer les fichiers utilisateur appropris (au format
-    texte)  l'aide de l'outil htdigest.
    
-
-    
    Exemple :
    <Location /private/>
-    AuthType Digest
-    AuthName "private area"
-    AuthDigestDomain /private/ http://mirror.my.dom/private2/
-    
-    AuthDigestProvider file
-    AuthUserFile /web/auth/.digest_pw
-    Require valid-user
-</Location>
    
-
    
-
-    
    Note
    
-    
    L'authentification  base de condens a t conue pour amliorer
-    la scurit par rapport  l'authentification basique, mais il
-    s'avre que ce but n'a pas t atteint. Un attaquant de type
-    "man-in-the-middle" peut facilement forcer le navigateur  revenir 
-    une authentification basique. Mme une oreille indiscrte passive
-    peut retrouver le mot de passe par force brute avec les moyens
-    modernes, car l'algorithme de hashage utilis par l'authentification
-     base de condens est trop rapide. Autre problme, le stockage des
-    mots de passe sur le serveur n'est pas sr. Le contenu d'un fichier
-    htdigest vol peut tre utilis directement pour l'authentification
-     base de condens. Il est donc fortement recommand d'utiliser
-    mod_ssl pour chiffrer la connexion.
    
-    
    mod_auth_digest ne fonctionne correctement que
-    sur les plates-formes o APR supporte la mmoire partage.
    
-    
    
 
    
 
 
    
diff --git a/docs/manual/mod/mod_auth_digest.html.ko.euc-kr b/docs/manual/mod/mod_auth_digest.html.ko.euc-kr
index e79a403995..ccdc540b07 100644
--- a/docs/manual/mod/mod_auth_digest.html.ko.euc-kr
+++ b/docs/manual/mod/mod_auth_digest.html.ko.euc-kr
@@ -39,7 +39,11 @@
     
      HTTP Digest Authentication Ѵ.
     ׷  ׽Ʈ ġ   ̴.
    
 
    
-
    þ
    
+
 
    top
    
+
    
+
    Digest Authentication ϱ
    
+
+    
    MD5 Digest authentication ſ    ִ.
+    AuthType Basic AuthBasicProvider 
+    AuthType Digest AuthDigestProvider
+    Ͽ     ִ. ׸ ּ ȣϷ
+     ⺻ URI AuthDigestDomain þ Ѵ.
    
+
+    
    htdigest 
+    Ͽ  ()   ִ.
    
+
+    
    :
    
+      <Location /private/>
    
+      
+        AuthType Digest
    
+        AuthName "private area"
    
+        AuthDigestDomain /private/ http://mirror.my.dom/private2/
    
+	
    
+	AuthDigestProvider file
    
+        AuthUserFile /web/auth/.digest_pw
    
+        Require valid-user
    
+          
+      </Location>
+    
    
+
+    
     
+    
    Digest authentication Basic authentication 
+    ,  ؾ Ѵ. 2002 11  digest
+    authentication ϴ  Amaya, Konqueror, (Windows
+    ǹڿ Բ ϸ ȵ - ذ Ʒ "MS Internet Explorer  ذϱ" )
+    Mac OS X Windows MS Internet
+    Explorer, Mozilla,
+    Netscape  7, Opera,
+    Safari  ִ.
+    lynx digest authentication
+     ʴ´. digest authentication
+    basic authentication ŭ θ  ʾұ⶧ 
+    ڰ ϴ  ϴ 쿡 ؾ
+    Ѵ.
    
+    
    
+
    top
    
+
    
+
    MS Internet Explorer  ذϱ
    
+    
     Windows Internet Explorer Digest authentication
+     ǹڿ ִ GET û RFC ٸ
+    óϴ  ִ.     ذ 
+    ִ.
    
+
+    
    
+    ù° α׷ ڷḦ Ѱֱ GET
+     POST û ϴ ̴.  
+    ϴٸ   ذå̴.
+    
    
+
+    
    , ġ 2.0.51 AuthDigestEnableQueryStringHack
+    ȯ溯 Ͽ  ذѴ. û
+    AuthDigestEnableQueryStringHack ϸ
+    ġ MSIE ׸ ذ ġ ϰ û URI digest
+    񱳿 Ѵ.     Ѵ.
    
+
+    
    MSIE Digest Authentication ϱ:
    
+    BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On
+    
    
+
+    
     ȯ溯   ڼ  BrowserMatch þ
+    ϶.
    
+
    
+
    top
    
 
    AuthDigestAlgorithm þ
    
 
  • mod_authz_groupfile
    • top
    
-
    AuthLDAPAuthorizePrefix Directive
    
-
    
 
    :digest authentication challenge response
@@ -246,75 +315,6 @@ URI
     
    
 
 
-
    top
    
-
    
-
    Digest Authentication ϱ
    
-
-    
    MD5 Digest authentication ſ    ִ.
-    AuthType Basic AuthBasicProvider 
-    AuthType Digest AuthDigestProvider
-    Ͽ     ִ. ׸ ּ ȣϷ
-     ⺻ URI AuthDigestDomain þ Ѵ.
    
-
-    
    htdigest 
-    Ͽ  ()   ִ.
    
-
-    
    :
    
-      <Location /private/>
    
-      
-        AuthType Digest
    
-        AuthName "private area"
    
-        AuthDigestDomain /private/ http://mirror.my.dom/private2/
    
-	
    
-	AuthDigestProvider file
    
-        AuthUserFile /web/auth/.digest_pw
    
-        Require valid-user
    
-          
-      </Location>
-    
    
-
-    
     
-    
    Digest authentication Basic authentication 
-    ,  ؾ Ѵ. 2002 11  digest
-    authentication ϴ  Amaya, Konqueror, (Windows
-    ǹڿ Բ ϸ ȵ - ذ Ʒ "MS Internet Explorer  ذϱ" )
-    Mac OS X Windows MS Internet
-    Explorer, Mozilla,
-    Netscape  7, Opera,
-    Safari  ִ.
-    lynx digest authentication
-     ʴ´. digest authentication
-    basic authentication ŭ θ  ʾұ⶧ 
-    ڰ ϴ  ϴ 쿡 ؾ
-    Ѵ.
    
-    
    
-
    top
    
-
    
-
    MS Internet Explorer  ذϱ
    
-    
     Windows Internet Explorer Digest authentication
-     ǹڿ ִ GET û RFC ٸ
-    óϴ  ִ.     ذ 
-    ִ.
    
-
-    
    
-    ù° α׷ ڷḦ Ѱֱ GET
-     POST û ϴ ̴.  
-    ϴٸ   ذå̴.
-    
    
-
-    
    , ġ 2.0.51 AuthDigestEnableQueryStringHack
-    ȯ溯 Ͽ  ذѴ. û
-    AuthDigestEnableQueryStringHack ϸ
-    ġ MSIE ׸ ذ ġ ϰ û URI digest
-    񱳿 Ѵ.     Ѵ.
    
-
-    
    MSIE Digest Authentication ϱ:
    
-    BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On
-    
    
-
-    
     ȯ溯   ڼ  BrowserMatch þ
-    ϶.
    
-
    
 
 
    
 
     :  en  |
diff --git a/docs/manual/mod/mod_auth_form.html.en b/docs/manual/mod/mod_auth_form.html.en
index 6eb6c9731a..58375e3e37 100644
--- a/docs/manual/mod/mod_auth_form.html.en
+++ b/docs/manual/mod/mod_auth_form.html.en
@@ -96,362 +96,6 @@
 
  • Authentication howto
    • 
 
    
 
    top
    
-
    AuthFormAuthoritative Directive
    
-
-
-
-
-
-
-
-
-
    Description:Sets whether authorization and authentication are passed to
-lower level modules
    Syntax:AuthFormAuthoritative On|Off
    Default:AuthFormAuthoritative On
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Base
    Module:mod_auth_form
    
-    
    Normally, each authorization module listed in AuthFormProvider will attempt
-    to verify the user, and if the user is not found in any provider,
-    access will be denied. Setting the
-    AuthFormAuthoritative directive explicitly
-    to Off allows for both authentication and
-    authorization to be passed on to other non-provider-based modules
-    if there is no userID or rule
-    matching the supplied userID.  This should only be necessary when
-    combining mod_auth_form with third-party modules
-    that are not configured with the AuthFormProvider
-    directive.  When using such modules, the order of processing
-    is determined in the modules' source code and is not configurable.
    
-
-
    
-
    top
    
-
    AuthFormBody Directive
    
-
-
-
-
-
-
-
-
-
    Description:The name of a form field carrying the body of the request to attempt on successful login
    Syntax:AuthFormBody fieldname
    Default:httpd_body
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
-    
    The AuthFormMethod directive specifies
-    the name of an HTML field which, if present, will contain the method of the request to
-    to submit should login be successful.
    
-
-    
    By populating the form with fields described by
-    AuthFormMethod,
-    AuthFormMimetype and
-    AuthFormBody, a website can retry
-    a request that may have been interrupted by the login screen, or by a session
-    timeout.
    
-
-
    
-
    top
    
-
    AuthFormDisableNoStore Directive
    
-
-
-
-
-
-
-
-
-
    Description:Disable the CacheControl no-store header on the login page
    Syntax:AuthFormDisableNoStore On|Off
    Default:AuthFormDisableNoStore Off
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
-    
    The AuthFormDisableNoStore flag
-    disables the sending of a Cache-Control no-store header with the
-    error 401 page returned when the user is not yet logged in. The purpose of the header
-    is to make it difficult for an ecmascript application to attempt to resubmit the
-    login form, and reveal the username and password to the backend application. Disable
-    at your own risk.
    
-
-
-
    
-
    top
    
-
    AuthFormFakeBasicAuth Directive
    
-
-
-
-
-
-
-
-
-
    Description:Fake a Basic Authentication header
    Syntax:AuthFormFakeBasicAuth On|Off
    Default:AuthFormFakeBasicAuth Off
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
-    
    The AuthFormFakeBasicAuth flag
-    determines whether a Basic Authentication header will be added to
-    the request headers. This can be used to expose the username and password to
-    an underlying application, without the underlying application having to be aware
-    of how the login was achieved.
    
-
-
-
    
-
    top
    
-
    AuthFormLocation Directive
    
-
-
-
-
-
-
-
-
-
    Description:The name of a form field carrying a URL to redirect to on successful login
    Syntax:AuthFormLocation fieldname
    Default:httpd_location
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
-    
    The AuthFormLocation directive specifies
-    the name of an HTML field which, if present, will contain a URL to redirect the browser to
-    should login be successful.
    
-
-
    
-
    top
    
-
    AuthFormLoginRequiredLocation Directive
    
-
-
-
-
-
-
-
-
-
    Description:The URL of the page to be redirected to should login be required
    Syntax:AuthFormLoginRequiredLocation url
    Default:none
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later. The use of the expression
-parser has been added in 2.4.4.
    
-    
    The AuthFormLoginRequiredLocation directive
-    specifies the URL to redirect to should the user not be authorised to view a page. The value
-    is parsed using the ap_expr parser before being sent to the client.
-    By default, if a user is not authorised to view a page, the HTTP response code
-    HTTP_UNAUTHORIZED will be returned with the page specified by the
-    ErrorDocument directive. This directive overrides this
-    default.
    
-
-    
    Use this directive if you have a dedicated login page to redirect users to.
    
-
-
-
    
-
    top
    
-
    AuthFormLoginSuccessLocation Directive
    
-
-
-
-
-
-
-
-
-
    Description:The URL of the page to be redirected to should login be successful
    Syntax:AuthFormLoginSuccessLocation url
    Default:none
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later. The use of the expression
-parser has been added in 2.4.4.
    
-    
    The AuthFormLoginSuccessLocation directive
-    specifies the URL to redirect to should the user have logged in successfully. The value is
-    parsed using the ap_expr parser before being sent to the client.
-    This directive can be overridden if a form field has been defined containing another URL
-    using the AuthFormLocation directive.
    
-
-    
    Use this directive if you have a dedicated login URL, and you have not embedded the
-    destination page in the login form.
    
-
-
-
    
-
    top
    
-
    AuthFormLogoutLocation Directive
    
-
-
-
-
-
-
-
-
-
    Description:The URL to redirect to after a user has logged out
    Syntax:AuthFormLogoutLocation uri
    Default:none
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later. The use of the expression
-parser has been added in 2.4.4.
    
-    
    The AuthFormLogoutLocation directive
-    specifies the URL of a page on the server to redirect to should the user attempt to log
-    out. The value is parsed using the ap_expr parser before
-    being sent to the client.
    
-
-    
    When a URI is accessed that is served by the handler form-logout-handler,
-    the page specified by this directive will be shown to the end user. For example:
    
-
-    
    Example
    <Location /logout>
-    SetHandler form-logout-handler
-    AuthFormLogoutLocation "http://example.com/loggedout.html"
-    Session on
-    #...
-</Location>
    
-
    
-
-    
    An attempt to access the URI /logout/ will result in the user being logged
-    out, and the page /loggedout.html will be displayed. Make sure that the page
-    loggedout.html is not password protected, otherwise the page will not be
-    displayed.
    
-
-
-
    
-
    top
    
-
    AuthFormMethod Directive
    
-
-
-
-
-
-
-
-
-
    Description:The name of a form field carrying the method of the request to attempt on successful login
    Syntax:AuthFormMethod fieldname
    Default:httpd_method
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
-    
    The AuthFormMethod directive specifies
-    the name of an HTML field which, if present, will contain the method of the request to
-    to submit should login be successful.
    
-
-    
    By populating the form with fields described by
-    AuthFormMethod,
-    AuthFormMimetype and
-    AuthFormBody, a website can retry
-    a request that may have been interrupted by the login screen, or by a session
-    timeout.
    
-
-
    
-
    top
    
-
    AuthFormMimetype Directive
    
-
-
-
-
-
-
-
-
-
    Description:The name of a form field carrying the mimetype of the body of the request to attempt on successful login
    Syntax:AuthFormMimetype fieldname
    Default:httpd_mimetype
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
-    
    The AuthFormMethod directive specifies
-    the name of an HTML field which, if present, will contain the
-    mimetype of the request to to submit should login be successful.
    
-
-    
    By populating the form with fields described by
-    AuthFormMethod,
-    AuthFormMimetype and
-    AuthFormBody, a website can retry
-    a request that may have been interrupted by the login screen, or by a session
-    timeout.
    
-
-
    
-
    top
    
-
    AuthFormPassword Directive
    
-
-
-
-
-
-
-
-
-
    Description:The name of a form field carrying the login password
    Syntax:AuthFormPassword fieldname
    Default:httpd_password
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
-    
    The AuthFormPassword directive specifies
-    the name of an HTML field which, if present, will contain the password to be used to log
-    in.
    
-
-
    
-
    top
    
-
    AuthFormProvider Directive
    
-
-
-
-
-
-
-
-
-
    Description:Sets the authentication provider(s) for this location
    Syntax:AuthFormProvider provider-name
-[provider-name] ...
    Default:AuthFormProvider file
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Base
    Module:mod_auth_form
    
-    
    The AuthFormProvider directive sets
-    which provider is used to authenticate the users for this location.
-    The default file provider is implemented
-    by the mod_authn_file module.  Make sure
-    that the chosen provider module is present in the server.
    
-
-    
    Example
    <Location /secure>
-    AuthType form
-    AuthName "private area"
-    AuthFormProvider  dbm
-    AuthDBMType        SDBM
-    AuthDBMUserFile    "/www/etc/dbmpasswd"
-    Require            valid-user
-    #...
-</Location>
    
-
    
-
-    
    Providers are implemented by mod_authn_dbm,
-    mod_authn_file, mod_authn_dbd,
-    mod_authnz_ldap and mod_authn_socache.
    
-
-
    
-
    top
    
-
    AuthFormSitePassphrase Directive
    
-
-
-
-
-
-
-
-
-
    Description:Bypass authentication checks for high traffic sites
    Syntax:AuthFormSitePassphrase secret
    Default:none
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
-    
    The AuthFormSitePassphrase directive
-    specifies a passphrase which, if present in the user session, causes Apache httpd to
-    bypass authentication checks for the given URL. It can be used on high traffic websites
-    to reduce the load induced on authentication infrastructure.
    
-
-    
    The passphrase can be inserted into a user session by adding this directive to the
-    configuration for the form-login-handler. The form-login-handler
-    itself will always run the authentication checks, regardless of whether a passphrase
-    is specified or not.
    
-
-    
    Warning
    
-      
    If the session is exposed to the user through the use of
-      mod_session_cookie, and the session is not protected with
-      mod_session_crypto, the passphrase is open to potential exposure
-      through a dictionary attack. Regardless of how the session is configured,
-      ensure that this directive is not used within URL spaces where private user data
-      could be exposed, or sensitive transactions can be conducted. Use at own risk.
    
-    
    
-
-
-
    
-
    top
    
-
    AuthFormSize Directive
    
-
-
-
-
-
-
-
-
-
    Description:The largest size of the form in bytes that will be parsed for the login details
    Syntax:AuthFormSize size
    Default:8192
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
-    
    The AuthFormSize directive specifies
-    the maximum size of the body of the request that will be parsed to find the login form.
    
-
-    
    If a login request arrives that exceeds this size, the whole request will be aborted
-    with the HTTP response code HTTP_REQUEST_TOO_LARGE.
    
-
-    
    If you have populated the form with fields described by
-    AuthFormMethod,
-    AuthFormMimetype and
-    AuthFormBody, you probably want to set this
-    field to a similar size as the KeptBodySize
-    directive.
    
-
-
-
    
-
    top
    
-
    AuthFormUsername Directive
    
-
-
-
-
-
-
-
-
-
    Description:The name of a form field carrying the login username
    Syntax:AuthFormUsername fieldname
    Default:httpd_username
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
-    
    The AuthFormUsername directive specifies
-    the name of an HTML field which, if present, will contain the username to be used to log
-    in.
    
-
-
    
-
    top
    
 
    
 
    Basic Configuration
    
 
@@ -698,6 +342,362 @@ SessionCryptoPassphrase secret
     pick usernames and passwords that avoid characters that are
     URLencoded in form submission, or you may get unexpected results.
    
     
    
+
    top
    
+
    AuthFormAuthoritative Directive
    
+
+
+
+
+
+
+
+
+
    Description:Sets whether authorization and authentication are passed to
+lower level modules
    Syntax:AuthFormAuthoritative On|Off
    Default:AuthFormAuthoritative On
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Base
    Module:mod_auth_form
    
+    
    Normally, each authorization module listed in AuthFormProvider will attempt
+    to verify the user, and if the user is not found in any provider,
+    access will be denied. Setting the
+    AuthFormAuthoritative directive explicitly
+    to Off allows for both authentication and
+    authorization to be passed on to other non-provider-based modules
+    if there is no userID or rule
+    matching the supplied userID.  This should only be necessary when
+    combining mod_auth_form with third-party modules
+    that are not configured with the AuthFormProvider
+    directive.  When using such modules, the order of processing
+    is determined in the modules' source code and is not configurable.
    
+
+
    
+
    top
    
+
    AuthFormBody Directive
    
+
+
+
+
+
+
+
+
+
    Description:The name of a form field carrying the body of the request to attempt on successful login
    Syntax:AuthFormBody fieldname
    Default:httpd_body
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
+    
    The AuthFormMethod directive specifies
+    the name of an HTML field which, if present, will contain the method of the request to
+    to submit should login be successful.
    
+
+    
    By populating the form with fields described by
+    AuthFormMethod,
+    AuthFormMimetype and
+    AuthFormBody, a website can retry
+    a request that may have been interrupted by the login screen, or by a session
+    timeout.
    
+
+
    
+
    top
    
+
    AuthFormDisableNoStore Directive
    
+
+
+
+
+
+
+
+
+
    Description:Disable the CacheControl no-store header on the login page
    Syntax:AuthFormDisableNoStore On|Off
    Default:AuthFormDisableNoStore Off
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
+    
    The AuthFormDisableNoStore flag
+    disables the sending of a Cache-Control no-store header with the
+    error 401 page returned when the user is not yet logged in. The purpose of the header
+    is to make it difficult for an ecmascript application to attempt to resubmit the
+    login form, and reveal the username and password to the backend application. Disable
+    at your own risk.
    
+
+
+
    
+
    top
    
+
    AuthFormFakeBasicAuth Directive
    
+
+
+
+
+
+
+
+
+
    Description:Fake a Basic Authentication header
    Syntax:AuthFormFakeBasicAuth On|Off
    Default:AuthFormFakeBasicAuth Off
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
+    
    The AuthFormFakeBasicAuth flag
+    determines whether a Basic Authentication header will be added to
+    the request headers. This can be used to expose the username and password to
+    an underlying application, without the underlying application having to be aware
+    of how the login was achieved.
    
+
+
+
    
+
    top
    
+
    AuthFormLocation Directive
    
+
+
+
+
+
+
+
+
+
    Description:The name of a form field carrying a URL to redirect to on successful login
    Syntax:AuthFormLocation fieldname
    Default:httpd_location
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
+    
    The AuthFormLocation directive specifies
+    the name of an HTML field which, if present, will contain a URL to redirect the browser to
+    should login be successful.
    
+
+
    
+
    top
    
+
    AuthFormLoginRequiredLocation Directive
    
+
+
+
+
+
+
+
+
+
    Description:The URL of the page to be redirected to should login be required
    Syntax:AuthFormLoginRequiredLocation url
    Default:none
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later. The use of the expression
+parser has been added in 2.4.4.
    
+    
    The AuthFormLoginRequiredLocation directive
+    specifies the URL to redirect to should the user not be authorised to view a page. The value
+    is parsed using the ap_expr parser before being sent to the client.
+    By default, if a user is not authorised to view a page, the HTTP response code
+    HTTP_UNAUTHORIZED will be returned with the page specified by the
+    ErrorDocument directive. This directive overrides this
+    default.
    
+
+    
    Use this directive if you have a dedicated login page to redirect users to.
    
+
+
+
    
+
    top
    
+
    AuthFormLoginSuccessLocation Directive
    
+
+
+
+
+
+
+
+
+
    Description:The URL of the page to be redirected to should login be successful
    Syntax:AuthFormLoginSuccessLocation url
    Default:none
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later. The use of the expression
+parser has been added in 2.4.4.
    
+    
    The AuthFormLoginSuccessLocation directive
+    specifies the URL to redirect to should the user have logged in successfully. The value is
+    parsed using the ap_expr parser before being sent to the client.
+    This directive can be overridden if a form field has been defined containing another URL
+    using the AuthFormLocation directive.
    
+
+    
    Use this directive if you have a dedicated login URL, and you have not embedded the
+    destination page in the login form.
    
+
+
+
    
+
    top
    
+
    AuthFormLogoutLocation Directive
    
+
+
+
+
+
+
+
+
+
    Description:The URL to redirect to after a user has logged out
    Syntax:AuthFormLogoutLocation uri
    Default:none
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later. The use of the expression
+parser has been added in 2.4.4.
    
+    
    The AuthFormLogoutLocation directive
+    specifies the URL of a page on the server to redirect to should the user attempt to log
+    out. The value is parsed using the ap_expr parser before
+    being sent to the client.
    
+
+    
    When a URI is accessed that is served by the handler form-logout-handler,
+    the page specified by this directive will be shown to the end user. For example:
    
+
+    
    Example
    <Location "/logout">
+    SetHandler form-logout-handler
+    AuthFormLogoutLocation "http://example.com/loggedout.html"
+    Session on
+    #...
+</Location>
    
+
    
+
+    
    An attempt to access the URI /logout/ will result in the user being logged
+    out, and the page /loggedout.html will be displayed. Make sure that the page
+    loggedout.html is not password protected, otherwise the page will not be
+    displayed.
    
+
+
+
    
+
    top
    
+
    AuthFormMethod Directive
    
+
+
+
+
+
+
+
+
+
    Description:The name of a form field carrying the method of the request to attempt on successful login
    Syntax:AuthFormMethod fieldname
    Default:httpd_method
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
+    
    The AuthFormMethod directive specifies
+    the name of an HTML field which, if present, will contain the method of the request to
+    to submit should login be successful.
    
+
+    
    By populating the form with fields described by
+    AuthFormMethod,
+    AuthFormMimetype and
+    AuthFormBody, a website can retry
+    a request that may have been interrupted by the login screen, or by a session
+    timeout.
    
+
+
    
+
    top
    
+
    AuthFormMimetype Directive
    
+
+
+
+
+
+
+
+
+
    Description:The name of a form field carrying the mimetype of the body of the request to attempt on successful login
    Syntax:AuthFormMimetype fieldname
    Default:httpd_mimetype
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
+    
    The AuthFormMethod directive specifies
+    the name of an HTML field which, if present, will contain the
+    mimetype of the request to to submit should login be successful.
    
+
+    
    By populating the form with fields described by
+    AuthFormMethod,
+    AuthFormMimetype and
+    AuthFormBody, a website can retry
+    a request that may have been interrupted by the login screen, or by a session
+    timeout.
    
+
+
    
+
    top
    
+
    AuthFormPassword Directive
    
+
+
+
+
+
+
+
+
+
    Description:The name of a form field carrying the login password
    Syntax:AuthFormPassword fieldname
    Default:httpd_password
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
+    
    The AuthFormPassword directive specifies
+    the name of an HTML field which, if present, will contain the password to be used to log
+    in.
    
+
+
    
+
    top
    
+
    AuthFormProvider Directive
    
+
+
+
+
+
+
+
+
+
    Description:Sets the authentication provider(s) for this location
    Syntax:AuthFormProvider provider-name
+[provider-name] ...
    Default:AuthFormProvider file
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Base
    Module:mod_auth_form
    
+    
    The AuthFormProvider directive sets
+    which provider is used to authenticate the users for this location.
+    The default file provider is implemented
+    by the mod_authn_file module.  Make sure
+    that the chosen provider module is present in the server.
    
+
+    
    Example
    <Location "/secure">
+    AuthType form
+    AuthName "private area"
+    AuthFormProvider  dbm
+    AuthDBMType        SDBM
+    AuthDBMUserFile    "/www/etc/dbmpasswd"
+    Require            valid-user
+    #...
+</Location>
    
+
    
+
+    
    Providers are implemented by mod_authn_dbm,
+    mod_authn_file, mod_authn_dbd,
+    mod_authnz_ldap and mod_authn_socache.
    
+
+
    
+
    top
    
+
    AuthFormSitePassphrase Directive
    
+
+
+
+
+
+
+
+
+
    Description:Bypass authentication checks for high traffic sites
    Syntax:AuthFormSitePassphrase secret
    Default:none
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
+    
    The AuthFormSitePassphrase directive
+    specifies a passphrase which, if present in the user session, causes Apache httpd to
+    bypass authentication checks for the given URL. It can be used on high traffic websites
+    to reduce the load induced on authentication infrastructure.
    
+
+    
    The passphrase can be inserted into a user session by adding this directive to the
+    configuration for the form-login-handler. The form-login-handler
+    itself will always run the authentication checks, regardless of whether a passphrase
+    is specified or not.
    
+
+    
    Warning
    
+      
    If the session is exposed to the user through the use of
+      mod_session_cookie, and the session is not protected with
+      mod_session_crypto, the passphrase is open to potential exposure
+      through a dictionary attack. Regardless of how the session is configured,
+      ensure that this directive is not used within URL spaces where private user data
+      could be exposed, or sensitive transactions can be conducted. Use at own risk.
    
+    
    
+
+
+
    
+
    top
    
+
    AuthFormSize Directive
    
+
+
+
+
+
+
+
+
+
    Description:The largest size of the form in bytes that will be parsed for the login details
    Syntax:AuthFormSize size
    Default:8192
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
+    
    The AuthFormSize directive specifies
+    the maximum size of the body of the request that will be parsed to find the login form.
    
+
+    
    If a login request arrives that exceeds this size, the whole request will be aborted
+    with the HTTP response code HTTP_REQUEST_TOO_LARGE.
    
+
+    
    If you have populated the form with fields described by
+    AuthFormMethod,
+    AuthFormMimetype and
+    AuthFormBody, you probably want to set this
+    field to a similar size as the KeptBodySize
+    directive.
    
+
+
+
    
+
    top
    
+
    AuthFormUsername Directive
    
+
+
+
+
+
+
+
+
+
    Description:The name of a form field carrying the login username
    Syntax:AuthFormUsername fieldname
    Default:httpd_username
    Context:directory
    Status:Base
    Module:mod_auth_form
    Compatibility:Available in Apache HTTP Server 2.3.0 and later
    
+    
    The AuthFormUsername directive specifies
+    the name of an HTML field which, if present, will contain the username to be used to log
+    in.
    
+
+
    
 
 
    
 
    Available Languages:  en  |
diff --git a/docs/manual/mod/mod_auth_form.html.fr b/docs/manual/mod/mod_auth_form.html.fr
index 1d47e5d234..6c88bd5dbb 100644
--- a/docs/manual/mod/mod_auth_form.html.fr
+++ b/docs/manual/mod/mod_auth_form.html.fr
@@ -67,7 +67,17 @@
     
    
 
 
    
-
    Directives
    
+
 
    top
    
+
    
+
    Configuration de base
    
+
+      
    Pour protger une URL particulire avec le module
+      mod_auth_form, vous devez dterminer l'endroit o
+      vous allez stocker votre session, ainsi que la mthode
+      d'authentification. Dans cet exemple simple, les informations de
+      connexion sont stockes dans une session  l'aide du module
+      mod_session_cookie, et l'authentification utilise
+      un fichier en s'appuyant sur le module
+      mod_authn_file. Si l'authentification choue,
+      l'utilisateur dera redirig vers la page du formulaire de
+      connexion.
    
+
+      
    Exemple simple
    AuthFormProvider file
+AuthUserFile conf/passwd
+AuthType form
+AuthName realm
+AuthFormLoginRequiredLocation http://example.com/login.html
+Session On
+SessionCookieName session path=/
+SessionCryptoPassphrase secret
    
+
    
+
+      
    L'authentification mod_auth_form est active
+      en affectant la valeur form  la directive AuthType. Les directives
+      AuthFormProvider et
+      AuthUserFile
+      spcifient que les noms d'utilisateurs et mots de passe seront
+      vrifis en utilisant le fichier choisi.
    
+
+      
    Les directives Session, SessionCookieName et
+      SessionCryptoPassphrase
+      crent une session chiffre stocke dans un cookie HTTP au niveau
+      du navigateur. Pour plus d'informations  propos des diffrentes
+      options de configuration des sessions, reportez-vous  la
+      documentation du module mod_session.
    
+
+      
    Dans l'exemple simple ci-dessus, une URL a t protge par
+      mod_auth_form, mais on doit maintenant fournir
+       l'utilisateur un moyen d'entrer un nom et un mot de passe.  cet
+      effet, on peut soit crire une page de connexion indpendante
+      ddie, soit inclure le formulaire de connexion dans la page
+      courante.
    
+    
    top
    
+
    
+
    Page de connexion ddie
    
+
+      
    Le formulaire de connexion peut tre contenu dans une page
+      indpendante, ou tre inclus dans la page courante. 
    
+
+      
    Lorsque la connexion s'effectue  partir d'une page
+      indpendante et si la tentative d'authentification choue,
+      l'utilisateur doit tre redirig vers un formulaire de connexion,
+      cr  cet effet sur le site web, en utilisant la directive
+      AuthFormLoginRequiredLocation.
+      En gnral, la page de connexion contiendra un formulaire HTML
+      demandant  l'utilisateur de fournir un nom et un mot de passe.
    
+
+      
    Exemple de formulaire de connexion
    <form method="POST" action="/dologin.html">
+  Username: <input type="text" name="httpd_username" value="" />
+  Password: <input type="password" name="httpd_password" value="" />
+  <input type="submit" name="login" value="Login" />
+</form>
    
+
    
+
+      
    La partie o s'effectue la connexion proprement dite est
+      traite par le gestionnaire form-login-handler.
+      L'action de ce formulaire doit pointer vers ce gestionnaire, ce
+      que l'on configure dans Apache httpd comme suit :
    
+
+      
    Exemple de configuration du gestionnaire de
+      formulaire de connexion
    <Location /dologin.html>
+    SetHandler form-login-handler
+    AuthFormLoginRequiredLocation http://example.com/login.html
+    AuthFormLoginSuccessLocation http://example.com/success.html
+    AuthFormProvider file
+    AuthUserFile conf/passwd
+    AuthType form
+    AuthName realm
+    Session On
+    SessionCookieName session path=/
+    SessionCryptoPassphrase secret
+</Location>
    
+
    
+
+      
    L'URL spcifie par la directive
+      AuthFormLoginRequiredLocation
+      rfrencera en gnral une page expliquant  l'utilisateur que sa
+      tentative de connexion a chou, et qu'il doit la renouveler. La
+      directive AuthFormLoginSuccessLocation
+      spcifie l'URL vers laquelle l'utilisateur doit tre redirig s'il
+      s'est authentifi avec succs.
    
+
+      
    Alternativement, l'URL vers laquelle doit tre redirig
+      l'utilisateur s'il s'est authentifi avec succs peut tre
+      intgre dans le formulaire de connexion, comme dans l'exemple
+      ci-dessous. Il en dcoule que le mme gestionnaire
+      form-login-handler pourra tre utilis pour diffrentes
+      zones du site web.
    
+
+      
    Exemple de formulaire d'authentification multizone
    <form method="POST" action="/dologin.html">
+  Username: <input type="text" name="httpd_username" value="" />
+  Password: <input type="password" name="httpd_password" value="" />
+  <input type="submit" name="login" value="Login" />
+  <input type="hidden" name="httpd_location" value="http://example.com/success.html" />
+</form>
    
+
    
+
+    
    top
    
+
    
+
    Connexion  la vole
    
+
+      
    Avertissement
    
+        
    Il existe un risque, dans certaines circonstances, que le
+	formulaire de connexion configur pour une connexion  la vole
+	soit soumis plusieurs fois, rvlant de ce fait les paramtres
+	de connexion  l'application sous-jacente. L'administrateur doit
+	s'assurer que cette dernire est correctement scurise afin
+	d'viter les ventuels abus. En cas de doute, utilisez une page
+	de connexion indpendante ddie.
    
+      
    
+
+      
    Comme alternative  la page de connexion ddie pour un site
+      web, il est possible de configurer mod_auth_form
+      pour authentifier les utilisateurs  la vole, sans les rediriger
+      vers une autre page, ce qui permet de conserver l'tat de la page
+      courante au cours de la tentative de connexion. Ceci peut s'avrer
+      utile dans le cas d'une session limite dans le temps, si le dlai
+      de la session a expir pendant la requte de l'utilisateur. Ce
+      dernier peut alors se rauthentifier  la mme place, et
+      poursuivre son activit  partir du point o il en tait rest.
    
+
+      
    Si un utilisateur non authentifi tente d'accder  une page
+      protge par mod_auth_form, et si ce dernier
+      n'est pas configur avec une directive AuthFormLoginRequiredLocation,
+      un code de statut HTTP_UNAUTHORIZED est renvoy vers le
+      navigateur, indiquant  l'utilisateur qu'il n'est pas autoris 
+      accder  cette page.
    
+
+      
    Pour configurer l'authentification  la vole, l'administrateur
+      remplace le message d'erreur renvoy par le code de statut
+      HTTP_UNAUTHORIZED par un message d'erreur personnalis
+      contenant le formulaire de connexion comme suit :
    
+
+      
    Exemple simple d'authentification  la vole
    AuthFormProvider file
+ErrorDocument 401 /login.shtml
+AuthUserFile conf/passwd
+AuthType form
+AuthName realm
+AuthFormLoginRequiredLocation http://example.com/login.html
+Session On
+SessionCookieName session path=/
+SessionCryptoPassphrase secret
    
+
    
+
+      
    La page du message d'erreur doit contenir un formulaire de
+      connexion dont la proprit action est vide, comme dans l'exemple
+      ci-dessous. Ceci a pour effet de soumettre le formulaire  l'URL
+      protge originale, cette dernire n'ayant pas besoin d'tre
+      connue de la page en cours.
    
+
+      
    Exemple de formulaire de connexion  la vole
    <form method="POST" action="">
+  Username: <input type="text" name="httpd_username" value="" />
+  Password: <input type="password" name="httpd_password" value="" />
+  <input type="submit" name="login" value="Login" />
+</form>
    
+
    
+
+      
    Lorsque l'utilisateur final a entr ses informations de
+      connexion, le formulaire effectue une requte HTTP POST pour l'URL
+      originale protge par mot de passe.
+      mod_auth_form va alors intercepter cette requte
+      POST, et dans le cas o des champs HTML Utilisateur et Mot de
+      passe corrects sont prsents, l'utilisateur sera connect, et
+      l'URL originale protge par mot de passe lui sera retourne en
+      tant que requte GET.
    
+
+    
    top
    
+
    
+
    Connexion  la vole avec
+    conservation du contenu
    
+
+      
    Il existe une limite  la technique de connexion  la vole
+      dcrite ci-dessus ; si un formulaire HTML POST entrane une
+      demande d'authentification ou de rauthentification, le contenu du
+      formulaire original envoy par le navigateur sera perdu. Cela peut
+      s'avrer plus ou moins gnant pour l'utilisateur final selon la
+      fonction du site web.
    
+
+      
    Comme solution  ce problme, mod_auth_form
+      permet d'intgrer la mthode et le contenu de la requte originale
+      dans le formulaire de connexion. Si l'authentification russit,
+      Apache httpd pourra refaire une tentative avec la mthode et le contenu
+      originaux, tout en conservant l'tat de la requte originale.
    
+
+      
    Pour mettre en oeuvre la conservation du contenu, vous devez
+      ajouter trois champs supplmentaires au formulaire de connexion
+      comme dans l'exemple suivant :
    
+
+      
    Exemple de formulaire avec conservation du
+      contenu
    <form method="POST" action="">
+  Username: <input type="text" name="httpd_username" value="" />
+  Password: <input type="password" name="httpd_password" value="" />
+  <input type="submit" name="login" value="Login" />
+  
      <input type="hidden" name="httpd_method" value="POST" />
+  <input type="hidden" name="httpd_mimetype" value="application/x-www-form-urlencoded" />
+  <input type="hidden" name="httpd_body" value="name1=value1&name2=value2" />
    
+</form>
    
+
    
+
+      
    La manire dont la mthode, le type MIME et le contenu de la
+      requte originale seront intgrs dans le formulaire de connexion
+      vont dpendre de la plate-forme et de la technologie utilises au
+      sein du site web.
+      
    
+
+      
    Une option consiste  utiliser le module
+      mod_include en association avec la directive
+      KeptBodySize, ainsi
+      qu'un script CGI adapt pour intgrer les variables dans le
+      formulaire.
    
+
+      
    Une autre option consiste  prsenter le formulaire de
+      connexion en utilisant un script CGI ou une autre technologie
+      dynamique.
    
+
+      
    Exemple avec script CGI
            AuthFormProvider file
+        ErrorDocument 401 /cgi-bin/login.cgi
+        ...
    
+
    
+
+    
    top
    
+
    
+
    Dconnexion
    
+
+      
    Pour permettre  un utilisateur de se dconnecter d'une session
+      particulire, vous devez configurer une page pour qu'elle soit
+      traite par le gestionnaire form-logout-handler. Tout
+      accs  cette URL va entraner la suppression de l'Utilisateur et
+      du Mot de passe de la session courante, ce qui aura pour effet de
+      dconnecter l'utilisateur.
    
+
+      
    Vous pouvez spcifier une URL vers laquelle le navigateur sera
+      redirig en cas de dconnection russie, en dfinissant la
+      directive AuthFormLogoutLocation. Cette
+      URL devra expliquer  l'utilisateur qu'il a t dconnect, et lui
+      donner la possibilit de se connecter  nouveau.
    
+
+      
    Exemple simple de configuration de la
+      dconnexion
    SetHandler form-logout-handler
+AuthName realm
+AuthFormLogoutLocation http://example.com/loggedout.html
+Session On
+SessionCookieName session path=/
+SessionCryptoPassphrase secret
    
+
    
+
+      
    Notez que la dconnexion d'un utilisateur ne supprime pas la
+      session ; elle supprime seulement l'utilisateur et le mot de passe
+      de la session. Si la session qui en rsulte est vide, elle sera
+      probablement supprime, mais ce n'est pas garanti. Si vous voulez
+      tre sr que la session sera supprime, affectez une valeur faible
+       la directive SessionMaxAge, par exemple 1
+      (affecter  cette directive la valeur zro signifie une session
+      sans limite d'ge).
+      
    
+
+      
    Exemple simple avec dure de validit de session
+      limite
    SetHandler form-logout-handler
+AuthFormLogoutLocation http://example.com/loggedout.html
+Session On
+SessionMaxAge 1
+SessionCookieName session path=/
+SessionCryptoPassphrase secret
    
+
    
+
+    
    top
    
+
    
+
    Noms d'utilisateurs et mots de
+    passe
    
+    
    Notez que la soumission d'un formulaire implique l'encodage URL
+    (URLEncoding) des donnes du formulaire, ici le nom d'utilisateur et
+    le mot de passe. Vous devez donc choisir des noms d'utilisateurs et
+    mots de passe qui ne contiennent pas de caractres susceptibles
+    d'tre encods URL lors de la soumission du formulaire, sous peine
+    d'obtenir des rsultats inattendus.
    
+    
    
+
    top
    
 
    Directive AuthFormAuthoritative
    
 
     d'utilisateur qui sera utilis pour la connexion.
    
-
    top
    
-
    
-
    Configuration de base
    
-
-      
    Pour protger une URL particulire avec le module
-      mod_auth_form, vous devez dterminer l'endroit o
-      vous allez stocker votre session, ainsi que la mthode
-      d'authentification. Dans cet exemple simple, les informations de
-      connexion sont stockes dans une session  l'aide du module
-      mod_session_cookie, et l'authentification utilise
-      un fichier en s'appuyant sur le module
-      mod_authn_file. Si l'authentification choue,
-      l'utilisateur dera redirig vers la page du formulaire de
-      connexion.
    
-
-      
    Exemple simple
    AuthFormProvider file
-AuthUserFile conf/passwd
-AuthType form
-AuthName realm
-AuthFormLoginRequiredLocation http://example.com/login.html
-Session On
-SessionCookieName session path=/
-SessionCryptoPassphrase secret
    
-
    
-
-      
    L'authentification mod_auth_form est active
-      en affectant la valeur form  la directive AuthType. Les directives
-      AuthFormProvider et
-      AuthUserFile
-      spcifient que les noms d'utilisateurs et mots de passe seront
-      vrifis en utilisant le fichier choisi.
    
-
-      
    Les directives Session, SessionCookieName et
-      SessionCryptoPassphrase
-      crent une session chiffre stocke dans un cookie HTTP au niveau
-      du navigateur. Pour plus d'informations  propos des diffrentes
-      options de configuration des sessions, reportez-vous  la
-      documentation du module mod_session.
    
-
-      
    Dans l'exemple simple ci-dessus, une URL a t protge par
-      mod_auth_form, mais on doit maintenant fournir
-       l'utilisateur un moyen d'entrer un nom et un mot de passe.  cet
-      effet, on peut soit crire une page de connexion indpendante
-      ddie, soit inclure le formulaire de connexion dans la page
-      courante.
    
-    
    top
    
-
    
-
    Page de connexion ddie
    
-
-      
    Le formulaire de connexion peut tre contenu dans une page
-      indpendante, ou tre inclus dans la page courante. 
    
-
-      
    Lorsque la connexion s'effectue  partir d'une page
-      indpendante et si la tentative d'authentification choue,
-      l'utilisateur doit tre redirig vers un formulaire de connexion,
-      cr  cet effet sur le site web, en utilisant la directive
-      AuthFormLoginRequiredLocation.
-      En gnral, la page de connexion contiendra un formulaire HTML
-      demandant  l'utilisateur de fournir un nom et un mot de passe.
    
-
-      
    Exemple de formulaire de connexion
    <form method="POST" action="/dologin.html">
-  Username: <input type="text" name="httpd_username" value="" />
-  Password: <input type="password" name="httpd_password" value="" />
-  <input type="submit" name="login" value="Login" />
-</form>
    
-
    
-
-      
    La partie o s'effectue la connexion proprement dite est
-      traite par le gestionnaire form-login-handler.
-      L'action de ce formulaire doit pointer vers ce gestionnaire, ce
-      que l'on configure dans Apache httpd comme suit :
    
-
-      
    Exemple de configuration du gestionnaire de
-      formulaire de connexion
    <Location /dologin.html>
-    SetHandler form-login-handler
-    AuthFormLoginRequiredLocation http://example.com/login.html
-    AuthFormLoginSuccessLocation http://example.com/success.html
-    AuthFormProvider file
-    AuthUserFile conf/passwd
-    AuthType form
-    AuthName realm
-    Session On
-    SessionCookieName session path=/
-    SessionCryptoPassphrase secret
-</Location>
    
-
    
-
-      
    L'URL spcifie par la directive
-      AuthFormLoginRequiredLocation
-      rfrencera en gnral une page expliquant  l'utilisateur que sa
-      tentative de connexion a chou, et qu'il doit la renouveler. La
-      directive AuthFormLoginSuccessLocation
-      spcifie l'URL vers laquelle l'utilisateur doit tre redirig s'il
-      s'est authentifi avec succs.
    
-
-      
    Alternativement, l'URL vers laquelle doit tre redirig
-      l'utilisateur s'il s'est authentifi avec succs peut tre
-      intgre dans le formulaire de connexion, comme dans l'exemple
-      ci-dessous. Il en dcoule que le mme gestionnaire
-      form-login-handler pourra tre utilis pour diffrentes
-      zones du site web.
    
-
-      
    Exemple de formulaire d'authentification multizone
    <form method="POST" action="/dologin.html">
-  Username: <input type="text" name="httpd_username" value="" />
-  Password: <input type="password" name="httpd_password" value="" />
-  <input type="submit" name="login" value="Login" />
-  <input type="hidden" name="httpd_location" value="http://example.com/success.html" />
-</form>
    
-
    
-
-    
    top
    
-
    
-
    Connexion  la vole
    
-
-      
    Avertissement
    
-        
    Il existe un risque, dans certaines circonstances, que le
-	formulaire de connexion configur pour une connexion  la vole
-	soit soumis plusieurs fois, rvlant de ce fait les paramtres
-	de connexion  l'application sous-jacente. L'administrateur doit
-	s'assurer que cette dernire est correctement scurise afin
-	d'viter les ventuels abus. En cas de doute, utilisez une page
-	de connexion indpendante ddie.
    
-      
    
-
-      
    Comme alternative  la page de connexion ddie pour un site
-      web, il est possible de configurer mod_auth_form
-      pour authentifier les utilisateurs  la vole, sans les rediriger
-      vers une autre page, ce qui permet de conserver l'tat de la page
-      courante au cours de la tentative de connexion. Ceci peut s'avrer
-      utile dans le cas d'une session limite dans le temps, si le dlai
-      de la session a expir pendant la requte de l'utilisateur. Ce
-      dernier peut alors se rauthentifier  la mme place, et
-      poursuivre son activit  partir du point o il en tait rest.
    
-
-      
    Si un utilisateur non authentifi tente d'accder  une page
-      protge par mod_auth_form, et si ce dernier
-      n'est pas configur avec une directive AuthFormLoginRequiredLocation,
-      un code de statut HTTP_UNAUTHORIZED est renvoy vers le
-      navigateur, indiquant  l'utilisateur qu'il n'est pas autoris 
-      accder  cette page.
    
-
-      
    Pour configurer l'authentification  la vole, l'administrateur
-      remplace le message d'erreur renvoy par le code de statut
-      HTTP_UNAUTHORIZED par un message d'erreur personnalis
-      contenant le formulaire de connexion comme suit :
    
-
-      
    Exemple simple d'authentification  la vole
    AuthFormProvider file
-ErrorDocument 401 /login.shtml
-AuthUserFile conf/passwd
-AuthType form
-AuthName realm
-AuthFormLoginRequiredLocation http://example.com/login.html
-Session On
-SessionCookieName session path=/
-SessionCryptoPassphrase secret
    
-
    
-
-      
    La page du message d'erreur doit contenir un formulaire de
-      connexion dont la proprit action est vide, comme dans l'exemple
-      ci-dessous. Ceci a pour effet de soumettre le formulaire  l'URL
-      protge originale, cette dernire n'ayant pas besoin d'tre
-      connue de la page en cours.
    
-
-      
    Exemple de formulaire de connexion  la vole
    <form method="POST" action="">
-  Username: <input type="text" name="httpd_username" value="" />
-  Password: <input type="password" name="httpd_password" value="" />
-  <input type="submit" name="login" value="Login" />
-</form>
    
-
    
-
-      
    Lorsque l'utilisateur final a entr ses informations de
-      connexion, le formulaire effectue une requte HTTP POST pour l'URL
-      originale protge par mot de passe.
-      mod_auth_form va alors intercepter cette requte
-      POST, et dans le cas o des champs HTML Utilisateur et Mot de
-      passe corrects sont prsents, l'utilisateur sera connect, et
-      l'URL originale protge par mot de passe lui sera retourne en
-      tant que requte GET.
    
-
-    
    top
    
-
    
-
    Connexion  la vole avec
-    conservation du contenu
    
-
-      
    Il existe une limite  la technique de connexion  la vole
-      dcrite ci-dessus ; si un formulaire HTML POST entrane une
-      demande d'authentification ou de rauthentification, le contenu du
-      formulaire original envoy par le navigateur sera perdu. Cela peut
-      s'avrer plus ou moins gnant pour l'utilisateur final selon la
-      fonction du site web.
    
-
-      
    Comme solution  ce problme, mod_auth_form
-      permet d'intgrer la mthode et le contenu de la requte originale
-      dans le formulaire de connexion. Si l'authentification russit,
-      Apache httpd pourra refaire une tentative avec la mthode et le contenu
-      originaux, tout en conservant l'tat de la requte originale.
    
-
-      
    Pour mettre en oeuvre la conservation du contenu, vous devez
-      ajouter trois champs supplmentaires au formulaire de connexion
-      comme dans l'exemple suivant :
    
-
-      
    Exemple de formulaire avec conservation du
-      contenu
    <form method="POST" action="">
-  Username: <input type="text" name="httpd_username" value="" />
-  Password: <input type="password" name="httpd_password" value="" />
-  <input type="submit" name="login" value="Login" />
-  
      <input type="hidden" name="httpd_method" value="POST" />
-  <input type="hidden" name="httpd_mimetype" value="application/x-www-form-urlencoded" />
-  <input type="hidden" name="httpd_body" value="name1=value1&name2=value2" />
    
-</form>
    
-
    
-
-      
    La manire dont la mthode, le type MIME et le contenu de la
-      requte originale seront intgrs dans le formulaire de connexion
-      vont dpendre de la plate-forme et de la technologie utilises au
-      sein du site web.
-      
    
-
-      
    Une option consiste  utiliser le module
-      mod_include en association avec la directive
-      KeptBodySize, ainsi
-      qu'un script CGI adapt pour intgrer les variables dans le
-      formulaire.
    
-
-      
    Une autre option consiste  prsenter le formulaire de
-      connexion en utilisant un script CGI ou une autre technologie
-      dynamique.
    
-
-      
    Exemple avec script CGI
            AuthFormProvider file
-        ErrorDocument 401 /cgi-bin/login.cgi
-        ...
    
-
    
-
-    
    top
    
-
    
-
    Dconnexion
    
-
-      
    Pour permettre  un utilisateur de se dconnecter d'une session
-      particulire, vous devez configurer une page pour qu'elle soit
-      traite par le gestionnaire form-logout-handler. Tout
-      accs  cette URL va entraner la suppression de l'Utilisateur et
-      du Mot de passe de la session courante, ce qui aura pour effet de
-      dconnecter l'utilisateur.
    
-
-      
    Vous pouvez spcifier une URL vers laquelle le navigateur sera
-      redirig en cas de dconnection russie, en dfinissant la
-      directive AuthFormLogoutLocation. Cette
-      URL devra expliquer  l'utilisateur qu'il a t dconnect, et lui
-      donner la possibilit de se connecter  nouveau.
    
-
-      
    Exemple simple de configuration de la
-      dconnexion
    SetHandler form-logout-handler
-AuthName realm
-AuthFormLogoutLocation http://example.com/loggedout.html
-Session On
-SessionCookieName session path=/
-SessionCryptoPassphrase secret
    
-
    
-
-      
    Notez que la dconnexion d'un utilisateur ne supprime pas la
-      session ; elle supprime seulement l'utilisateur et le mot de passe
-      de la session. Si la session qui en rsulte est vide, elle sera
-      probablement supprime, mais ce n'est pas garanti. Si vous voulez
-      tre sr que la session sera supprime, affectez une valeur faible
-       la directive SessionMaxAge, par exemple 1
-      (affecter  cette directive la valeur zro signifie une session
-      sans limite d'ge).
-      
    
-
-      
    Exemple simple avec dure de validit de session
-      limite
    SetHandler form-logout-handler
-AuthFormLogoutLocation http://example.com/loggedout.html
-Session On
-SessionMaxAge 1
-SessionCookieName session path=/
-SessionCryptoPassphrase secret
    
-
    
-
-    
    top
    
-
    
-
    Noms d'utilisateurs et mots de
-    passe
    
-    
    Notez que la soumission d'un formulaire implique l'encodage URL
-    (URLEncoding) des donnes du formulaire, ici le nom d'utilisateur et
-    le mot de passe. Vous devez donc choisir des noms d'utilisateurs et
-    mots de passe qui ne contiennent pas de caractres susceptibles
-    d'tre encods URL lors de la soumission du formulaire, sous peine
-    d'obtenir des rsultats inattendus.
    
-    
    
 
    Langues Disponibles:  en  |
diff --git a/docs/manual/mod/mod_auth_form.xml b/docs/manual/mod/mod_auth_form.xml
index 57450fd5ae..8f2dc1fe24 100644
--- a/docs/manual/mod/mod_auth_form.xml
+++ b/docs/manual/mod/mod_auth_form.xml
@@ -358,7 +358,7 @@ SessionCryptoPassphrase secret
 
     Example
     
-<Location /secure>
+<Location "/secure">
     AuthType form
     AuthName "private area"
     AuthFormProvider  dbm
@@ -634,7 +634,7 @@ parser has been added in 2.4.4.
 
     Example
     
-<Location /logout>
+<Location "/logout">
     SetHandler form-logout-handler
     AuthFormLogoutLocation "http://example.com/loggedout.html"
     Session on
diff --git a/docs/manual/mod/mod_authn_anon.html.en b/docs/manual/mod/mod_authn_anon.html.en
index 8d8076f66f..ed7c11af71 100644
--- a/docs/manual/mod/mod_authn_anon.html.en
+++ b/docs/manual/mod/mod_authn_anon.html.en
@@ -67,6 +67,49 @@
 
 
    top
    
+
    
+
    Example
    
+    
    The example below is combined with "normal" htpasswd-file based
+    authentication and allows users in additionally as 'guests' with the
+    following properties:
    
+
+    
      
+      
    • It insists that the user enters a userID.
+      (Anonymous_NoUserID)
      • 
+
+      
    • It insists that the user enters a password.
+      (Anonymous_MustGiveEmail)
      • 
+
+      
    • The password entered must be a valid email address, i.e.
+      contain at least one '@' and a '.'.
+      (Anonymous_VerifyEmail)
      • 
+
+      
    • The userID must be one of anonymous guest www test
+      welcome and comparison is not case
+      sensitive. (Anonymous)
      • 
+
+      
    • And the Email addresses entered in the passwd field are
+      logged to the error log file.
+      (Anonymous_LogEmail)
      • 
+    
    
+
+    
    Example
    <Directory "/var/www/html/private">
+    AuthName "Use 'anonymous' & Email address for guest entry"
+    AuthType Basic
+    AuthBasicProvider file anon
+    AuthUserFile "/path/to/your/.htpasswd"
+    
+    Anonymous_NoUserID off
+    Anonymous_MustGiveEmail on
+    Anonymous_VerifyEmail on
+    Anonymous_LogEmail on
+    Anonymous anonymous guest www test welcome
+    
+    Require valid-user
+</Directory>
    
+
    
+
    
+
    top
    Anonymous Directive
    
 
    
 
    Description:Dtermine si l'autorisation et l'authentification sont confis 
@@ -497,295 +786,6 @@ connexion
    
 
 
 
 
 
 
    
     at least one '@' and a '.' to encourage users to enter valid email
     addresses (see the above Anonymous_LogEmail).
    
 
-
-
    top
    
-
    
-
    Example
    
-    
    The example below is combined with "normal" htpasswd-file based
-    authentication and allows users in additionally as 'guests' with the
-    following properties:
    
-
-    
      
-      
    • It insists that the user enters a userID.
-      (Anonymous_NoUserID)
      • 
-
-      
    • It insists that the user enters a password.
-      (Anonymous_MustGiveEmail)
      • 
-
-      
    • The password entered must be a valid email address, i.e.
-      contain at least one '@' and a '.'.
-      (Anonymous_VerifyEmail)
      • 
-
-      
    • The userID must be one of anonymous guest www test
-      welcome and comparison is not case
-      sensitive. (Anonymous)
      • 
-
-      
    • And the Email addresses entered in the passwd field are
-      logged to the error log file.
-      (Anonymous_LogEmail)
      • 
-    
    
-
-    
    Example
    <Directory "/var/www/html/private">
-    AuthName "Use 'anonymous' & Email address for guest entry"
-    AuthType Basic
-    AuthBasicProvider file anon
-    AuthUserFile "/path/to/your/.htpasswd"
-    
-    Anonymous_NoUserID off
-    Anonymous_MustGiveEmail on
-    Anonymous_VerifyEmail on
-    Anonymous_LogEmail on
-    Anonymous anonymous guest www test welcome
-    
-    Require valid-user
-</Directory>
    
-
    
 
    
diff --git a/docs/manual/mod/mod_authn_anon.html.fr b/docs/manual/mod/mod_authn_anon.html.fr
index 959aceac65..2a645d6acf 100644
--- a/docs/manual/mod/mod_authn_anon.html.fr
+++ b/docs/manual/mod/mod_authn_anon.html.fr
@@ -59,7 +59,10 @@ authentifi
     module mod_authn_anon est invoqu en affectant la
     valeur anon  la directive AuthBasicProvider.
    
 
    
-
    Directives
    
+
    Sujets
    
+
    Directives
    
 
-
    Sujets
    
-
    
+
    
+
    top
    
+
    
+
    Exemple
    
+    
    L'exemple ci-dessous prsente un exemple de combinaison avec
+    l'authentification  base de fichier htpasswd "normale", et permet
+    la connexion d'utilisateurs en tant qu'invits avec les proprits
+    suivantes :
    
+
+    
      
+      
    • Il incite l'utilisateur  fournir un identifiant.
+      (Anonymous_NoUserID)
      • 
+
+      
    • Il incite l'utilisateur  fournir un mot de passe.
+      (Anonymous_MustGiveEmail)
      • 
+
+      
    • Le mot de passe fourni doit tre une adresse email valide,
+      c'est  dire contenant au moins un '@' et un '.'.
+      (Anonymous_VerifyEmail)
      • 
+
+      
    • Les valeurs possibles pour l'identifiant utilisateur sont
+      anonymous, guest, www, test ou welcome, et la
+      vrification n'est pas sensible  la casse.
+      (Anonymous)
      • 
+
+      
    • Les adresses email entres dans le champ passwd sont
+      enregistres dans le fichier journal des erreurs.
+      (Anonymous_LogEmail)
      • 
+    
    
+
+    
    Exemple
    <Directory /var/www/html/private>
+    AuthName "Use 'anonymous' & Email address for guest entry"
+    AuthType Basic
+    AuthBasicProvider file anon
+    AuthUserFile /path/to/your/.htpasswd
+
+    Anonymous_NoUserID off
+    Anonymous_MustGiveEmail on
+    Anonymous_VerifyEmail on
+    Anonymous_LogEmail on
+    Anonymous anonymous guest www test welcome
+
+    Require valid-user
+</Directory>
    
+
    
+
    top
    Directive Anonymous
    
 
    
 
    Description:Specifies userIDs that are allowed access without
@@ -165,49 +208,6 @@ formatted email address
    
 
 
 
 
    
@@ -180,51 +225,6 @@ email fournie comme mot de passe est correct
     '.' afin d'inciter les utilisateurs  fournir des adresses email
     valides (voir ci-dessus la directive Anonymous_LogEmail).
    
 
-
-
    top
    
-
    
-
    Exemple
    
-    
    L'exemple ci-dessous prsente un exemple de combinaison avec
-    l'authentification  base de fichier htpasswd "normale", et permet
-    la connexion d'utilisateurs en tant qu'invits avec les proprits
-    suivantes :
    
-
-    
      
-      
    • Il incite l'utilisateur  fournir un identifiant.
-      (Anonymous_NoUserID)
      • 
-
-      
    • Il incite l'utilisateur  fournir un mot de passe.
-      (Anonymous_MustGiveEmail)
      • 
-
-      
    • Le mot de passe fourni doit tre une adresse email valide,
-      c'est  dire contenant au moins un '@' et un '.'.
-      (Anonymous_VerifyEmail)
      • 
-
-      
    • Les valeurs possibles pour l'identifiant utilisateur sont
-      anonymous, guest, www, test ou welcome, et la
-      vrification n'est pas sensible  la casse.
-      (Anonymous)
      • 
-
-      
    • Les adresses email entres dans le champ passwd sont
-      enregistres dans le fichier journal des erreurs.
-      (Anonymous_LogEmail)
      • 
-    
    
-
-    
    Exemple
    <Directory /var/www/html/private>
-    AuthName "Use 'anonymous' & Email address for guest entry"
-    AuthType Basic
-    AuthBasicProvider file anon
-    AuthUserFile /path/to/your/.htpasswd
-
-    Anonymous_NoUserID off
-    Anonymous_MustGiveEmail on
-    Anonymous_VerifyEmail on
-    Anonymous_LogEmail on
-    Anonymous anonymous guest www test welcome
-
-    Require valid-user
-</Directory>
    
-
    
 
    
diff --git a/docs/manual/mod/mod_authn_anon.html.ja.utf8 b/docs/manual/mod/mod_authn_anon.html.ja.utf8
index c145264dc0..2e1033cff4 100644
--- a/docs/manual/mod/mod_authn_anon.html.ja.utf8
+++ b/docs/manual/mod/mod_authn_anon.html.ja.utf8
@@ -59,7 +59,10 @@
     AuthBasicProvider に
     anon という値を設定することで起動されます。
    
 
    
-
    ディレクティブ
    
+
    トピック
    
+
    ディレクティブ
    
 
-
    トピック
    
-
    
+
    
+
    top
    
+
    
+
    例
    
+    
    以下の例は「普通」の htpasswd ファイルに基づいた認証と組み合わされて
+    おり、以下の要件を見たすユーザを「ゲスト」として許可します:
    
+
+    
      
+      
    • ユーザは userID を入力しなければなりません。
+      (Anonymous_NoUserID)
      • 
+
+      
    • ユーザはパスワードを入力しなければなりません。
+      (Anonymous_MustGiveEmail)
      • 
+
+      
    • 入力されたパスワードは有効な電子メールアドレスでなければ
+      なりません。すなわち、少くとも一つの '@' と '.' が
+      含まれている必要があります。
+      (Anonymous_VerifyEmail)
      • 
+
+      
    • userID は anonymous guest www test
+      welcome のどれかでなければなりません。
+      ユーザ名の比較は大文字小文字を区別しません。
      • 
+
+      
    • パスワード欄に入力された電子メールアドレスはエラーログファイルに
+      ロギングされます。
+      (Anonymous_LogEmail)
      • 
+    
    
+
+    
    例
    <Directory /var/www/html/private>
+    AuthName "Use 'anonymous' & Email address for guest entry"
+    AuthType Basic
+    AuthBasicProvider file anon
+    AuthUserFile /path/to/your/.htpasswd
+    
+    Anonymous_NoUserID off
+    Anonymous_MustGiveEmail on
+    Anonymous_VerifyEmail on
+    Anonymous_LogEmail on
+    Anonymous anonymous guest www test welcome
+    
+    Require valid-user
+</Directory>
    
+
    
+
    top
    Anonymous ディレクティブ
    
 
    
 
 
 
 
    
@@ -169,49 +212,6 @@
     少なくとも一つの '@' と '.' を含んでいるかどうかを調べます
     (上の Anonymous_LogEmail 参照)。
    
 
-
-
    top
    
-
    
-
    例
    
-    
    以下の例は「普通」の htpasswd ファイルに基づいた認証と組み合わされて
-    おり、以下の要件を見たすユーザを「ゲスト」として許可します:
    
-
-    
      
-      
    • ユーザは userID を入力しなければなりません。
-      (Anonymous_NoUserID)
      • 
-
-      
    • ユーザはパスワードを入力しなければなりません。
-      (Anonymous_MustGiveEmail)
      • 
-
-      
    • 入力されたパスワードは有効な電子メールアドレスでなければ
-      なりません。すなわち、少くとも一つの '@' と '.' が
-      含まれている必要があります。
-      (Anonymous_VerifyEmail)
      • 
-
-      
    • userID は anonymous guest www test
-      welcome のどれかでなければなりません。
-      ユーザ名の比較は大文字小文字を区別しません。
      • 
-
-      
    • パスワード欄に入力された電子メールアドレスはエラーログファイルに
-      ロギングされます。
-      (Anonymous_LogEmail)
      • 
-    
    
-
-    
    例
    <Directory /var/www/html/private>
-    AuthName "Use 'anonymous' & Email address for guest entry"
-    AuthType Basic
-    AuthBasicProvider file anon
-    AuthUserFile /path/to/your/.htpasswd
-    
-    Anonymous_NoUserID off
-    Anonymous_MustGiveEmail on
-    Anonymous_VerifyEmail on
-    Anonymous_LogEmail on
-    Anonymous anonymous guest www test welcome
-    
-    Require valid-user
-</Directory>
    
-
    
 
    
diff --git a/docs/manual/mod/mod_authn_anon.html.ko.euc-kr b/docs/manual/mod/mod_authn_anon.html.ko.euc-kr
index 686d382397..915848e0bc 100644
--- a/docs/manual/mod/mod_authn_anon.html.ko.euc-kr
+++ b/docs/manual/mod/mod_authn_anon.html.ko.euc-kr
@@ -53,7 +53,10 @@
     
    mod_auth_basic Ҷ AuthBasicProvider
      anon ϸ   Ѵ.
    
 
    
-
+
    top
    
+
    
+
    
+    
      "Ϲ" htpasswd-ϱ  ߰
+    ڰ   Ѵٸ 'մ(guest)' 
+     ֵ Ѵ:
    
+
+    
+
+    
    
+      <Directory /foo>
+      
+        AuthName "մ 湮Ϸ 'anonymous' ڿ ּҸ ϶"
    
+        AuthType Basic
    
+        AuthBasicProvider file anon
    
+        AuthUserFile /path/to/your/.htpasswd
    
+        
    
+        Anonymous_NoUserID off
    
+        Anonymous_MustGiveEmail on
    
+        Anonymous_VerifyEmail on
    
+        Anonymous_LogEmail on
    
+        Anonymous anonymous guest www test welcome
    
+        
    
+        Order Deny,Allow
    
+        Allow from all
    
+        
    
+        Require valid-user
    
+          
+      </Directory>
+    
    
+
    top
    Anonymous þ
    
 
    
 
 
 
 
    
@@ -161,51 +206,6 @@
     ϴ ˻Ѵ ( Anonymous_LogEmail ).
    
-
    top
    
-
    
-
    
-    
      "Ϲ" htpasswd-ϱ  ߰
-    ڰ   Ѵٸ 'մ(guest)' 
-     ֵ Ѵ:
    
-
-    
-
-    
    
-      <Directory /foo>
-      
-        AuthName "մ 湮Ϸ 'anonymous' ڿ ּҸ ϶"
    
-        AuthType Basic
    
-        AuthBasicProvider file anon
    
-        AuthUserFile /path/to/your/.htpasswd
    
-        
    
-        Anonymous_NoUserID off
    
-        Anonymous_MustGiveEmail on
    
-        Anonymous_VerifyEmail on
    
-        Anonymous_LogEmail on
    
-        Anonymous anonymous guest www test welcome
    
-        
    
-        Order Deny,Allow
    
-        Allow from all
    
-        
    
-        Require valid-user
    
-          
-      </Directory>
-    
    
-
    
 
     :  en  |
diff --git a/docs/manual/mod/mod_authn_core.html.en b/docs/manual/mod/mod_authn_core.html.en
index 42800860bd..4192656142 100644
--- a/docs/manual/mod/mod_authn_core.html.en
+++ b/docs/manual/mod/mod_authn_core.html.en
@@ -50,6 +50,78 @@
 
 
    top
    
+
    
+
    Creating Authentication Provider Aliases
    
+
+    
    Extended authentication providers can be created
+    within the configuration file and assigned an alias name.  The alias
+    providers can then be referenced through the directives
+    AuthBasicProvider or
+    AuthDigestProvider in
+    the same way as a base authentication provider.  Besides the ability
+    to create and alias an extended provider, it also allows the same
+    extended authentication provider to be reference by multiple
+    locations.
    
+
+    
    Examples
    
+
+        
    This example checks for passwords in two different text
+        files.
    
+
+        
    Checking multiple text password files
    # Check here first
+<AuthnProviderAlias file file1>
+    AuthUserFile "/www/conf/passwords1"
+</AuthnProviderAlias>
+
+# Then check here
+<AuthnProviderAlias file file2>   
+    AuthUserFile "/www/conf/passwords2"
+</AuthnProviderAlias>
+
+<Directory "/var/web/pages/secure">
+    AuthBasicProvider file1 file2
+    
+    AuthType Basic
+    AuthName "Protected Area"
+    Require valid-user
+</Directory>
    
+
    
+
+        
    The example below creates two different ldap authentication
+        provider aliases based on the ldap provider.  This allows
+        a single authenticated location to be serviced by multiple ldap
+        hosts:
    
+
+        
    Checking multiple LDAP servers
    <AuthnProviderAlias ldap ldap-alias1>
+    AuthLDAPBindDN "cn=youruser,o=ctx"
+    AuthLDAPBindPassword yourpassword
+    AuthLDAPURL "ldap://ldap.host/o=ctx"
+</AuthnProviderAlias>
+<AuthnProviderAlias ldap ldap-other-alias>
+    AuthLDAPBindDN "cn=yourotheruser,o=dev"
+    AuthLDAPBindPassword yourotherpassword
+    AuthLDAPURL "ldap://other.ldap.host/o=dev?cn"
+</AuthnProviderAlias>
+
+Alias "/secure" "/webpages/secure"
+<Directory "/webpages/secure">
+    Order deny,allow
+    Allow from all
+    
+    AuthBasicProvider ldap-other-alias  ldap-alias1
+    
+    AuthType Basic
+    AuthName "LDAP Protected Place"
+    Require valid-user
+    # Note that Require ldap-* would not work here, since the 
+    # AuthnProviderAlias does not provide the config to authorization providers
+    # that are implemented in the same module as the authentication provider.
+</Directory>
    
+
    
+    
+
+
    
+
    top
    AuthName Directive
    
 
    
 
 
 
 
 
 
  • Authentication, Authorization,
     and Access Control
    • 
-
-
    top
    
-
    
-
    Creating Authentication Provider Aliases
    
-
-    
    Extended authentication providers can be created
-    within the configuration file and assigned an alias name.  The alias
-    providers can then be referenced through the directives
-    AuthBasicProvider or
-    AuthDigestProvider in
-    the same way as a base authentication provider.  Besides the ability
-    to create and alias an extended provider, it also allows the same
-    extended authentication provider to be reference by multiple
-    locations.
    
-
-    
    Examples
    
-
-        
    This example checks for passwords in two different text
-        files.
    
-
-        
    Checking multiple text password files
    # Check here first
-<AuthnProviderAlias file file1>
-    AuthUserFile "/www/conf/passwords1"
-</AuthnProviderAlias>
-
-# Then check here
-<AuthnProviderAlias file file2>   
-    AuthUserFile "/www/conf/passwords2"
-</AuthnProviderAlias>
-
-<Directory "/var/web/pages/secure">
-    AuthBasicProvider file1 file2
-    
-    AuthType Basic
-    AuthName "Protected Area"
-    Require valid-user
-</Directory>
    
-
    
-
-        
    The example below creates two different ldap authentication
-        provider aliases based on the ldap provider.  This allows
-        a single authenticated location to be serviced by multiple ldap
-        hosts:
    
-
-        
    Checking multiple LDAP servers
    <AuthnProviderAlias ldap ldap-alias1>
-    AuthLDAPBindDN "cn=youruser,o=ctx"
-    AuthLDAPBindPassword yourpassword
-    AuthLDAPURL "ldap://ldap.host/o=ctx"
-</AuthnProviderAlias>
-<AuthnProviderAlias ldap ldap-other-alias>
-    AuthLDAPBindDN "cn=yourotheruser,o=dev"
-    AuthLDAPBindPassword yourotherpassword
-    AuthLDAPURL "ldap://other.ldap.host/o=dev?cn"
-</AuthnProviderAlias>
-
-Alias "/secure" "/webpages/secure"
-<Directory "/webpages/secure">
-    Order deny,allow
-    Allow from all
-    
-    AuthBasicProvider ldap-other-alias  ldap-alias1
-    
-    AuthType Basic
-    AuthName "LDAP Protected Place"
-    Require valid-user
-    # Note that Require ldap-* would not work here, since the 
-    # AuthnProviderAlias does not provide the config to authorization providers
-    # that are implemented in the same module as the authentication provider.
-</Directory>
    
-
    
-    
-
 
    
diff --git a/docs/manual/mod/mod_authn_core.html.fr b/docs/manual/mod/mod_authn_core.html.fr
index 72d5537fe3..26b30bd014 100644
--- a/docs/manual/mod/mod_authn_core.html.fr
+++ b/docs/manual/mod/mod_authn_core.html.fr
@@ -42,17 +42,95 @@
     mod_authn_core sont communes  tous les
     fournisseurs d'authentification.
    
 
    
-
+
    top
    
+
    
+
    Cration d'alias de fournisseurs
+d'authentification
    
+
+    
    Il est possible de crer des fournisseurs d'authentification
+    tendus dans le fichier de configuration et de leur assigner un
+    alias. Le fournisseur ainsi nomm peut alors tre rfrenc  l'aide
+    des directives AuthBasicProvider ou AuthDigestProvider tout comme
+    un fournisseur d'authentification de base. Outre la possibilit de
+    crer et attribuer un alias  un fournisseur tendu, le mme
+    fournisseur d'authentification peut aussi tre rfrenc par
+    plusieurs sections relatives  une zone du site web.
    
+
+    
    Exemples
    
+
+	
    Cet exemple vrifie les mots de passe dans deux fichiers
+	textes diffrents.
    
+
+	
    Vrification dans plusieurs fichiers de mots de
+	passe au format texte
    # Premire vrification
+<AuthnProviderAlias file file1>
+    AuthUserFile /www/conf/passwords1
+</AuthnProviderAlias>
+
+# Vrification suivante
+<AuthnProviderAlias file file2>   
+    AuthUserFile /www/conf/passwords2
+</AuthnProviderAlias>
+
+<Directory /var/web/pages/secure>
+    AuthBasicProvider file1 file2
+    
+    AuthType Basic
+    AuthName "Protected Area"
+    Require valid-user
+</Directory>
    
+
    
+
+
+
+        
    Dans l'exemple ci-dessous, deux fournisseurs
+	d'authentification ldap sont crs  partir du fournisseur ldap
+	de base, et se voient attribuer un alias. L'authentification
+	d'une mme zone peut alors tre traite par plusieurs serveurs
+	ldap :
    
+
+        
    Vrification auprs de plusieurs serveurs
+	LDAP
    <AuthnProviderAlias ldap ldap-alias1>
+    AuthLDAPBindDN cn=youruser,o=ctx
+    AuthLDAPBindPassword yourpassword
+    AuthLDAPURL ldap://ldap.host/o=ctx
+    </AuthnProviderAlias>
+    <AuthnProviderAlias ldap ldap-other-alias>
+    AuthLDAPBindDN cn=yourotheruser,o=dev
+    AuthLDAPBindPassword yourotherpassword
+    AuthLDAPURL ldap://other.ldap.host/o=dev?cn
+</AuthnProviderAlias>
+
+Alias /secure /webpages/secure
+<Directory /webpages/secure>
+    Order deny,allow
+    Allow from all
+    
+    AuthBasicProvider ldap-other-alias  ldap-alias1
+    
+    AuthType Basic
+    AuthName LDAP_Protected Place
+    Require valid-user
+    # Notez que Require ldap-* ne fonctionnerait pas ici, car
+    # AuthnProviderAlias ne fournit pas de configuration pour les
+    # fournisseurs d'autorisation implments dans le mme module que le
+    # fournisseur d'authentification.
+</Directory>
    
+
    
+    
+
+
    top
    Directive AuthName
    
 
    
 
    Description:Authorization realm for use in HTTP
@@ -176,78 +248,6 @@ the specified alias
    
 
 
 
 
 
 
    
@@ -186,84 +264,6 @@ l'alias sp
 
  • Authentification, autorisation et contrle
     d'accs
    • 
-
-
    top
    
-
    
-
    Cration d'alias de fournisseurs
-d'authentification
    
-
-    
    Il est possible de crer des fournisseurs d'authentification
-    tendus dans le fichier de configuration et de leur assigner un
-    alias. Le fournisseur ainsi nomm peut alors tre rfrenc  l'aide
-    des directives AuthBasicProvider ou AuthDigestProvider tout comme
-    un fournisseur d'authentification de base. Outre la possibilit de
-    crer et attribuer un alias  un fournisseur tendu, le mme
-    fournisseur d'authentification peut aussi tre rfrenc par
-    plusieurs sections relatives  une zone du site web.
    
-
-    
    Exemples
    
-
-	
    Cet exemple vrifie les mots de passe dans deux fichiers
-	textes diffrents.
    
-
-	
    Vrification dans plusieurs fichiers de mots de
-	passe au format texte
    # Premire vrification
-<AuthnProviderAlias file file1>
-    AuthUserFile /www/conf/passwords1
-</AuthnProviderAlias>
-
-# Vrification suivante
-<AuthnProviderAlias file file2>   
-    AuthUserFile /www/conf/passwords2
-</AuthnProviderAlias>
-
-<Directory /var/web/pages/secure>
-    AuthBasicProvider file1 file2
-    
-    AuthType Basic
-    AuthName "Protected Area"
-    Require valid-user
-</Directory>
    
-
    
-
-
-
-        
    Dans l'exemple ci-dessous, deux fournisseurs
-	d'authentification ldap sont crs  partir du fournisseur ldap
-	de base, et se voient attribuer un alias. L'authentification
-	d'une mme zone peut alors tre traite par plusieurs serveurs
-	ldap :
    
-
-        
    Vrification auprs de plusieurs serveurs
-	LDAP
    <AuthnProviderAlias ldap ldap-alias1>
-    AuthLDAPBindDN cn=youruser,o=ctx
-    AuthLDAPBindPassword yourpassword
-    AuthLDAPURL ldap://ldap.host/o=ctx
-    </AuthnProviderAlias>
-    <AuthnProviderAlias ldap ldap-other-alias>
-    AuthLDAPBindDN cn=yourotheruser,o=dev
-    AuthLDAPBindPassword yourotherpassword
-    AuthLDAPURL ldap://other.ldap.host/o=dev?cn
-</AuthnProviderAlias>
-
-Alias /secure /webpages/secure
-<Directory /webpages/secure>
-    Order deny,allow
-    Allow from all
-    
-    AuthBasicProvider ldap-other-alias  ldap-alias1
-    
-    AuthType Basic
-    AuthName LDAP_Protected Place
-    Require valid-user
-    # Notez que Require ldap-* ne fonctionnerait pas ici, car
-    # AuthnProviderAlias ne fournit pas de configuration pour les
-    # fournisseurs d'autorisation implments dans le mme module que le
-    # fournisseur d'authentification.
-</Directory>
    
-
    
-    
-
 
    
diff --git a/docs/manual/mod/mod_authn_dbd.html.en b/docs/manual/mod/mod_authn_dbd.html.en
index 703ddb9c18..065c53c56d 100644
--- a/docs/manual/mod/mod_authn_dbd.html.en
+++ b/docs/manual/mod/mod_authn_dbd.html.en
@@ -74,6 +74,81 @@
 
  • Password Formats
    • 
 
    top
    
+
    
+
    Performance and Cacheing
    
+
+
    Some users of DBD authentication in HTTPD 2.2/2.4 have reported that it
+imposes a problematic load on the database.  This is most likely where
+an HTML page contains hundreds of objects (e.g. images, scripts, etc)
+each of which requires authentication.  Users affected (or concerned)
+by this kind of problem should use mod_authn_socache
+to cache credentials and take most of the load off the database.
    
+
    top
    
+
    
+
    Configuration Example
    
+
+
    This simple example shows use of this module in the context of
+the Authentication and DBD frameworks.
    
+
    # mod_dbd configuration
+# UPDATED to include authentication cacheing
+DBDriver pgsql
+DBDParams "dbname=apacheauth user=apache password=xxxxxx"
+
+DBDMin  4
+DBDKeep 8
+DBDMax  20
+DBDExptime 300
+
+<Directory "/usr/www/myhost/private">
+  # mod_authn_core and mod_auth_basic configuration
+  # for mod_authn_dbd
+  AuthType Basic
+  AuthName "My Server"
+
+  # To cache credentials, put socache ahead of dbd here
+  AuthBasicProvider socache dbd
+
+  # Also required for caching: tell the cache to cache dbd lookups!
+  AuthnCacheProvideFor dbd
+  AuthnCacheContext my-server
+
+  # mod_authz_core configuration
+  Require valid-user
+
+  # mod_authn_dbd SQL query to authenticate a user
+  AuthDBDUserPWQuery "SELECT password FROM authn WHERE user = %s"
+</Directory>
    
+
+
    top
    
+
    
+
    Exposing Login Information
    
+
+
    
+If httpd was built against APR version 1.3.0
+or higher, then whenever a query is made to the database server, all
+column values in the first row returned by the query are placed in the
+environment, using environment variables with the prefix "AUTHENTICATE_".
+
    
+
    If a database query for example returned the username, full name
+and telephone number of a user, a CGI program will have access to
+this information without the need to make a second independent database
+query to gather this additional information.
    
+
    This has the potential to dramatically simplify the coding and
+configuration required in some web applications.
+
    
+
    top
    
+
    
+
    Preventing SQL injections
    
+
+  
    Whether you need to care about SQL security depends on what DBD driver
+  and backend you use.  With most drivers you don't have to do anything :
+  the statement is prepared by the database at startup, and user input is
+  used only as data.  But you may need to untaint your input.  At the time
+  of writing, the only driver that requires you to take care is FreeTDS.
    
+  
    Please read mod_dbd documentation for more information
+  about security on this scope.
    
+
    
+
    top
    AuthDBDUserPWQuery Directive
    
 
    
 
 
 
 
 
    
@@ -137,81 +212,6 @@
     more information.
    
-
    top
    
-
    
-
    Performance and Cacheing
    
-
-
    Some users of DBD authentication in HTTPD 2.2/2.4 have reported that it
-imposes a problematic load on the database.  This is most likely where
-an HTML page contains hundreds of objects (e.g. images, scripts, etc)
-each of which requires authentication.  Users affected (or concerned)
-by this kind of problem should use mod_authn_socache
-to cache credentials and take most of the load off the database.
    
-
    top
    
-
    
-
    Configuration Example
    
-
-
    This simple example shows use of this module in the context of
-the Authentication and DBD frameworks.
    
-
    # mod_dbd configuration
-# UPDATED to include authentication cacheing
-DBDriver pgsql
-DBDParams "dbname=apacheauth user=apache password=xxxxxx"
-
-DBDMin  4
-DBDKeep 8
-DBDMax  20
-DBDExptime 300
-
-<Directory /usr/www/myhost/private>
-  # mod_authn_core and mod_auth_basic configuration
-  # for mod_authn_dbd
-  AuthType Basic
-  AuthName "My Server"
-
-  # To cache credentials, put socache ahead of dbd here
-  AuthBasicProvider socache dbd
-
-  # Also required for caching: tell the cache to cache dbd lookups!
-  AuthnCacheProvideFor dbd
-  AuthnCacheContext my-server
-
-  # mod_authz_core configuration
-  Require valid-user
-
-  # mod_authn_dbd SQL query to authenticate a user
-  AuthDBDUserPWQuery "SELECT password FROM authn WHERE user = %s"
-</Directory>
    
-
-
    top
    
-
    
-
    Exposing Login Information
    
-
-
    
-If httpd was built against APR version 1.3.0
-or higher, then whenever a query is made to the database server, all
-column values in the first row returned by the query are placed in the
-environment, using environment variables with the prefix "AUTHENTICATE_".
-
    
-
    If a database query for example returned the username, full name
-and telephone number of a user, a CGI program will have access to
-this information without the need to make a second independent database
-query to gather this additional information.
    
-
    This has the potential to dramatically simplify the coding and
-configuration required in some web applications.
-
    
-
    top
    
-
    
-
    Preventing SQL injections
    
-
-  
    Whether you need to care about SQL security depends on what DBD driver
-  and backend you use.  With most drivers you don't have to do anything :
-  the statement is prepared by the database at startup, and user input is
-  used only as data.  But you may need to untaint your input.  At the time
-  of writing, the only driver that requires you to take care is FreeTDS.
    
-  
    Please read mod_dbd documentation for more information
-  about security on this scope.
    
-
    
 
    Available Languages:  en  |
diff --git a/docs/manual/mod/mod_authn_dbd.html.fr b/docs/manual/mod/mod_authn_dbd.html.fr
index e4a127f927..7274e6d071 100644
--- a/docs/manual/mod/mod_authn_dbd.html.fr
+++ b/docs/manual/mod/mod_authn_dbd.html.fr
@@ -48,18 +48,18 @@ SQL
     mod_auth_digest, on peut invoquer ce module en
     affectant la valeur dbd  la directive AuthBasicProvider ou AuthDigestProvider.
    
 
    
-
    
 
    Description:SQL query to look up a password for a user
    
 
 
 
 
    
-
-
-
-
-
-
    Description:Requte SQL servant  vrifier le mot de passe d'un
-utilisateur
    Syntaxe:AuthDBDUserPWQuery requte
    Contexte:rpertoire
    Statut:Extension
    Module:mod_authn_dbd
    
-    
    La directive AuthDBDUserPWQuery permet de
-    spcifier une requte servant  vrifier le mot de passe d'un
-    utilisateur donn. L'identifiant utilisateur sera transmis comme
-    paramtre sous forme d'une seule chane de caractres lorsque la
-    requte sera excute. Cet identifiant est rfrenc dans la requte
-    en utilisant le spcificateur de format %s.
    
-    
    AuthDBDUserPWQuery "SELECT password FROM authn WHERE user = %s"
    
-
-    
    La premire colonne du premier enregistrement renvoy par la
-    requte se prsentera sous la forme d'une chane de caractres
-    contenant le mot de passe chiffr. Les enregistrements suivants sont
-    ignors. Si aucun enregistrement n'est renvoy, l'utilisateur ne
-    sera pas authentifi par mod_authn_dbd.
    
-    
    Si httpd a t compil avec la version 1.3.0 ou suprieure de
-    l'APR, toute valeur de colonne supplmentaire
-    du premier enregistrement renvoy par la requte sera stocke dans
-    une variable d'environnement dont le nom aura la forme
-    AUTHENTICATE_valeur-colonne.
-    
    
-    
    Le format du mot de passe chiffr dpend du frontal
-    d'authentification utilis (par exemple
-    mod_auth_basic ou
-    mod_auth_digest). Voir la documentation sur les Formats de mots de passe pour
-    plus de dtails.
    
-
-
    
-
    top
    
-
    Directive AuthDBDUserRealmQuery
    
-
-
-
-
-
-
-
    Description:Requte SQL servant  vrifier une empreinte de mot de
-passe pour un utilisateur et un identifiant d'authentification.
-
    Syntaxe:AuthDBDUserRealmQuery requte
    Contexte:rpertoire
    Statut:Extension
    Module:mod_authn_dbd
    
-    
    La directive AuthDBDUserRealmQuery spcifie
-    une requte SQL servant  vrifier une empreinte de mot
-    de passe pour un utilisateur et un identifiant d'authentification
-    donns au cours d'un processus d'authentification digest. Les
-    identifiants de l'utilisateur et de l'authentification
-    sont passs dans cet ordre comme paramtres  l'excution de la
-    requte. Ils sont rfrencs dans la chane de la requte en
-    utilisant des spcificateurs de format %s.
    
-    
    AuthDBDUserRealmQuery "SELECT password FROM authn WHERE user = %s AND realm = %s"
    
-
-    
    La premire colonne du premier enregistrement renvoy par la
-    requte se prsentera sous la forme d'une chane de caractres
-    contenant le mot de passe chiffr. Les enregistrements suivants
-    seront ignors. Si aucun enregistrement n'est renvoy, l'utilisateur
-    ne sera pas authentifi par mod_authn_dbd.
    
-    
    Si httpd a t compil avec une version 1.3.0 ou suprieure de
-    l'APR, toute valeur de colonne supplmentaire
-    du premier enregistrement renvoy par la requte sera stocke dans
-    une variable d'environnement avec un nom de la forme
-    AUTHENTICATE_COLONNE.
-    
    
-    
    Le format du mot de passe chiffr dpend du frontal
-    d'authentification utilis (par exemple
-    mod_auth_basic ou
-    mod_auth_digest). Voir la documentation sur les Formats de mots de passe pour
-    plus de dtails.
    
-
-
    
-
    top
    
 
    
 
    Performances et mise en cache
    
 
@@ -233,6 +158,81 @@ configuration n
   mod_dbd pour plus d'informations  propos de la
   scurit dans ce domaine.
    
 
    
+
    top
    
+
    Directive AuthDBDUserPWQuery
    
+
+
+
+
+
+
+
    Description:Requte SQL servant  vrifier le mot de passe d'un
+utilisateur
    Syntaxe:AuthDBDUserPWQuery requte
    Contexte:rpertoire
    Statut:Extension
    Module:mod_authn_dbd
    
+    
    La directive AuthDBDUserPWQuery permet de
+    spcifier une requte servant  vrifier le mot de passe d'un
+    utilisateur donn. L'identifiant utilisateur sera transmis comme
+    paramtre sous forme d'une seule chane de caractres lorsque la
+    requte sera excute. Cet identifiant est rfrenc dans la requte
+    en utilisant le spcificateur de format %s.
    
+    
    AuthDBDUserPWQuery "SELECT password FROM authn WHERE user = %s"
    
+
+    
    La premire colonne du premier enregistrement renvoy par la
+    requte se prsentera sous la forme d'une chane de caractres
+    contenant le mot de passe chiffr. Les enregistrements suivants sont
+    ignors. Si aucun enregistrement n'est renvoy, l'utilisateur ne
+    sera pas authentifi par mod_authn_dbd.
    
+    
    Si httpd a t compil avec la version 1.3.0 ou suprieure de
+    l'APR, toute valeur de colonne supplmentaire
+    du premier enregistrement renvoy par la requte sera stocke dans
+    une variable d'environnement dont le nom aura la forme
+    AUTHENTICATE_valeur-colonne.
+    
    
+    
    Le format du mot de passe chiffr dpend du frontal
+    d'authentification utilis (par exemple
+    mod_auth_basic ou
+    mod_auth_digest). Voir la documentation sur les Formats de mots de passe pour
+    plus de dtails.
    
+
+
    
+
    top
    
+
    Directive AuthDBDUserRealmQuery
    
+
+
+
+
+
+
+
    Description:Requte SQL servant  vrifier une empreinte de mot de
+passe pour un utilisateur et un identifiant d'authentification.
+
    Syntaxe:AuthDBDUserRealmQuery requte
    Contexte:rpertoire
    Statut:Extension
    Module:mod_authn_dbd
    
+    
    La directive AuthDBDUserRealmQuery spcifie
+    une requte SQL servant  vrifier une empreinte de mot
+    de passe pour un utilisateur et un identifiant d'authentification
+    donns au cours d'un processus d'authentification digest. Les
+    identifiants de l'utilisateur et de l'authentification
+    sont passs dans cet ordre comme paramtres  l'excution de la
+    requte. Ils sont rfrencs dans la chane de la requte en
+    utilisant des spcificateurs de format %s.
    
+    
    AuthDBDUserRealmQuery "SELECT password FROM authn WHERE user = %s AND realm = %s"
    
+
+    
    La premire colonne du premier enregistrement renvoy par la
+    requte se prsentera sous la forme d'une chane de caractres
+    contenant le mot de passe chiffr. Les enregistrements suivants
+    seront ignors. Si aucun enregistrement n'est renvoy, l'utilisateur
+    ne sera pas authentifi par mod_authn_dbd.
    
+    
    Si httpd a t compil avec une version 1.3.0 ou suprieure de
+    l'APR, toute valeur de colonne supplmentaire
+    du premier enregistrement renvoy par la requte sera stocke dans
+    une variable d'environnement avec un nom de la forme
+    AUTHENTICATE_COLONNE.
+    
    
+    
    Le format du mot de passe chiffr dpend du frontal
+    d'authentification utilis (par exemple
+    mod_auth_basic ou
+    mod_auth_digest). Voir la documentation sur les Formats de mots de passe pour
+    plus de dtails.
    
+
+
    
 
    
 
    
 
    Langues Disponibles:  en  |
diff --git a/docs/manual/mod/mod_authn_dbd.xml b/docs/manual/mod/mod_authn_dbd.xml
index 9eda1bf208..2ee2e9fa6d 100644
--- a/docs/manual/mod/mod_authn_dbd.xml
+++ b/docs/manual/mod/mod_authn_dbd.xml
@@ -82,7 +82,7 @@ DBDKeep 8
 DBDMax  20
 DBDExptime 300
 
-<Directory /usr/www/myhost/private>
+<Directory "/usr/www/myhost/private">
   # mod_authn_core and mod_auth_basic configuration
   # for mod_authn_dbd
   AuthType Basic
diff --git a/docs/manual/mod/mod_authn_dbm.html.en b/docs/manual/mod/mod_authn_dbm.html.en
index 66cf82cbc7..59671c91cf 100644
--- a/docs/manual/mod/mod_authn_dbm.html.en
+++ b/docs/manual/mod/mod_authn_dbm.html.en
@@ -66,6 +66,7 @@
 
  • htdbm
    • 
 
  • Password Formats
    • 
 
    
+
 
    top
    
 
    AuthDBMType Directive
    
 
@@ -137,7 +138,6 @@ passwords for authenticationhtdbm.
    
-
 
    
 
    Available Languages:  en  |
diff --git a/docs/manual/mod/mod_authn_dbm.html.fr b/docs/manual/mod/mod_authn_dbm.html.fr
index da49cd1670..fba73c24d2 100644
--- a/docs/manual/mod/mod_authn_dbm.html.fr
+++ b/docs/manual/mod/mod_authn_dbm.html.fr
@@ -66,6 +66,7 @@ passe
 
  • htpasswd
    • 
 
  • htdbm
    • 
 
    
+
 
    top
    Directive AuthDBMType
    
 
    
     
 
 
 
 
    
@@ -144,7 +145,6 @@ des utilisateurs et de leurs mots de passe
     utilitaire permettant de maintenir les fichiers DBM.
    
-
 
    
 
    Langues Disponibles:  en  |
diff --git a/docs/manual/mod/mod_authn_dbm.html.ja.utf8 b/docs/manual/mod/mod_authn_dbm.html.ja.utf8
index 797ea0ced7..1f2892ab15 100644
--- a/docs/manual/mod/mod_authn_dbm.html.ja.utf8
+++ b/docs/manual/mod/mod_authn_dbm.html.ja.utf8
@@ -68,6 +68,7 @@
   AuthDigestProvider
 
 
    
+
 
    top
    AuthDBMType ディレクティブ
    
 
    
 
 
 
 
    
@@ -131,7 +132,6 @@
     更新したりすることができます。
    
-
 
    
 
    翻訳済み言語:  en  |
diff --git a/docs/manual/mod/mod_authn_dbm.html.ko.euc-kr b/docs/manual/mod/mod_authn_dbm.html.ko.euc-kr
index 3b7cbd0492..82b3e74b4e 100644
--- a/docs/manual/mod/mod_authn_dbm.html.ko.euc-kr
+++ b/docs/manual/mod/mod_authn_dbm.html.ko.euc-kr
@@ -64,6 +64,7 @@
   AuthDigestProvider
 
 
    
+
 
    top
    AuthDBMType þ
    
 
    
 
 
 
 
    
@@ -123,7 +124,6 @@
     DBM ȣ  Ѵ.
    
-
 
    
 
     :  en  |
diff --git a/docs/manual/mod/mod_authn_file.html.en b/docs/manual/mod/mod_authn_file.html.en
index e9f8a77755..b221c885ba 100644
--- a/docs/manual/mod/mod_authn_file.html.en
+++ b/docs/manual/mod/mod_authn_file.html.en
@@ -62,6 +62,7 @@
 
  • htdigest
    • 
 
  • Password Formats
    • 
 
    
+
 
    top
    AuthUserFile Directive
    
 
    
 
 
 
 
    
@@ -127,7 +128,6 @@ passwords for authentication
-
 
    
 
    Available Languages:  en  |
diff --git a/docs/manual/mod/mod_authn_file.html.fr b/docs/manual/mod/mod_authn_file.html.fr
index 91dd1d299f..2eba3a8034 100644
--- a/docs/manual/mod/mod_authn_file.html.fr
+++ b/docs/manual/mod/mod_authn_file.html.fr
@@ -63,6 +63,7 @@ texte
 
  • Formats de mots de
 passe
    • 
 
    
+
 
    top
    Directive AuthUserFile
    
 
    
     
 
 
 
 
    
@@ -135,7 +136,6 @@ passe
-
 
    
 
    Langues Disponibles:  en  |
diff --git a/docs/manual/mod/mod_authn_file.html.ja.utf8 b/docs/manual/mod/mod_authn_file.html.ja.utf8
index 71dde525f8..30070d0155 100644
--- a/docs/manual/mod/mod_authn_file.html.ja.utf8
+++ b/docs/manual/mod/mod_authn_file.html.ja.utf8
@@ -67,6 +67,7 @@
 
  • htpasswd
    • 
 
  • htdigest
    • 
 
    
+
 
    top
    AuthUserFile ディレクティブ
    
 
    
     
 
 
 
 
    
@@ -138,7 +139,6 @@
     
-
 
    
 
    翻訳済み言語:  en  |
diff --git a/docs/manual/mod/mod_authn_file.html.ko.euc-kr b/docs/manual/mod/mod_authn_file.html.ko.euc-kr
index a0c8410e8c..e4cba5699f 100644
--- a/docs/manual/mod/mod_authn_file.html.ko.euc-kr
+++ b/docs/manual/mod/mod_authn_file.html.ko.euc-kr
@@ -63,6 +63,7 @@
 
  • htpasswd
    • 
 
  • htdigest
    • 
 
    
+
 
    top
    AuthUserFile þ
    
 
    
 
 
 
 
    
@@ -121,7 +122,6 @@
     
-
 
    
 
     :  en  |
diff --git a/docs/manual/mod/mod_authn_socache.html.en b/docs/manual/mod/mod_authn_socache.html.en
index fb4cd702ce..6a13c31ef0 100644
--- a/docs/manual/mod/mod_authn_socache.html.en
+++ b/docs/manual/mod/mod_authn_socache.html.en
@@ -53,6 +53,61 @@ the load on backends
 
 
    top
    
+
    
+
    Authentication Cacheing
    
+    
    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
+    in point is where an HTML page contains hundreds of objects
+    (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
+    maintaining a cache of authentication credentials.
    
+
    top
    
+
    
+
    Usage
    
+    
    The authentication cache should be used where authentication
+    lookups impose a significant load on the server, or a backend or
+    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).
+    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. 
+        
    2. List socache ahead of the provider you're
+            cacheing for in your AuthBasicProvider or AuthDigestProvider directive.
      3. 
+    
    
+    
    A simple usage example to accelerate mod_authn_dbd
+    using dbm as a cache engine:
    
+    
    #AuthnCacheSOCache is optional.  If specified, it is server-wide
+AuthnCacheSOCache dbm
+<Directory "/usr/www/myhost/private">
+    AuthType Basic
+    AuthName "Cached Authentication Example"
+    AuthBasicProvider socache dbd
+    AuthDBDUserPWQuery "SELECT password FROM authn WHERE user = %s"
+    AuthnCacheProvideFor dbd
+    Require valid-user
+    #Optional
+    AuthnCacheContext dbd-authn-example
+</Directory>
    
+
+
    top
    
+
    
+
    Cacheing with custom modules
    
+    
    Module developers should note that their modules must be enabled
+    for cacheing 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.
    
+
    
+
    top
    AuthnCacheContext Directive
    
 
    
 
 
 
 
 
    
@@ -167,61 +222,6 @@ Apache HTTP Server 2.4.7 and later
     your timeout.
    
-
    top
    
-
    
-
    Authentication Cacheing
    
-    
    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
-    in point is where an HTML page contains hundreds of objects
-    (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
-    maintaining a cache of authentication credentials.
    
-
    top
    
-
    
-
    Usage
    
-    
    The authentication cache should be used where authentication
-    lookups impose a significant load on the server, or a backend or
-    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).
-    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. 
-        
    2. List socache ahead of the provider you're
-            cacheing for in your AuthBasicProvider or AuthDigestProvider directive.
      3. 
-    
    
-    
    A simple usage example to accelerate mod_authn_dbd
-    using dbm as a cache engine:
    
-    
    #AuthnCacheSOCache is optional.  If specified, it is server-wide
-AuthnCacheSOCache dbm
-<Directory /usr/www/myhost/private>
-    AuthType Basic
-    AuthName "Cached Authentication Example"
-    AuthBasicProvider socache dbd
-    AuthDBDUserPWQuery "SELECT password FROM authn WHERE user = %s"
-    AuthnCacheProvideFor dbd
-    Require valid-user
-    #Optional
-    AuthnCacheContext dbd-authn-example
-</Directory>
    
-
-
    top
    
-
    
-
    Cacheing with custom modules
    
-    
    Module developers should note that their modules must be enabled
-    for cacheing 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 Languages:  en  |
diff --git a/docs/manual/mod/mod_authn_socache.html.fr b/docs/manual/mod/mod_authn_socache.html.fr
index 8368987404..768b64c341 100644
--- a/docs/manual/mod/mod_authn_socache.html.fr
+++ b/docs/manual/mod/mod_authn_socache.html.fr
@@ -38,7 +38,12 @@ la charge des serveurs d'arri
     
    Maintient un cache des donnes d'authentification pour limiter
     les sollicitations du serveur d'arrire-plan.
    
 
    
-
+
    top
    
+
    
+
    Mise en cache des donnes d'authentification
    
+    
    Certains utilisateurs qui mettent oeuvre une authentification
+    lourde s'appuyant par exemple sur des requtes SQL
+    (mod_authn_dbd) ont signal une charge induite
+    inacceptable sur leur fournisseur d'authentification. Cela se
+    produit typiquement dans le cas o une page HTML contient des
+    centaines d'objets (images, scripts, pages de styles, media,
+    etc...), et o une requte pour cette page gnre des centaines de
+    sous-requtes  effet immdiat pour des contenus supplmentaires
+    authentifis.
    
+    
    Pour rsoudre ce problme, mod_authn_socache fournit une solution
+    qui permet de maintenir un cache des donnes d'authentification.
    
+
    top
    
+
    
+
    Utilisation
    
+    
    Le cache d'authentification doit tre utilis lorsque les
+    requtes d'authentification induisent une charge significative sur le
+    serveur, le serveur d'arrire-plan ou le rseau. Cette mise en cache
+    n'apportera probablement aucune amlioration dans le cas d'une
+    authentification  base de fichier (mod_authn_file)
+    ou de base de donnes dbm (mod_authn_dbm) car ces
+    mthodes sont de par leur conception rapides et lgres (la mise en
+    cache peut cependant s'avrer utile dans le cas o le fichier est
+    situ sur un montage rseau). Les fournisseurs d'authentification
+    bass sur SQL ou LDAP ont plus de chances de tirer parti de cette
+    mise en cache, en particulier lorsqu'un problme de performances est
+    dtect. mod_authnz_ldap grant son propre cache,
+    seul mod_authn_dbd est concern par notre sujet.
    
+    
    Les principales rgles  appliquer pour la mise en cache sont :
    
+    
    1. Inclure le fournisseur pour lequel vous voulez effectuer une
+    mise en cache dans une directive
+    AuthnCacheProvideFor.
      2. 
+        
    2. Mettre socache avant le fournisseur pour lequel
+	vous voulez effectuer une mise en cache dans votre directive
+	AuthBasicProvider
+	ou AuthDigestProvider.
      3. 
+    
    
+    
    Voici un exemple simple permettant d'acclrer
+    mod_authn_dbd et utilisant dbm comme moteur de la
+    mise en cache :
    
+    
        #AuthnCacheSOCache est optionnel. S'il est dfini, il l'est pour
+    #l'ensemble du serveur
+AuthnCacheSOCache dbm
+<Directory /usr/www/myhost/private>
+    AuthType Basic
+    AuthName "Cached Authentication Example"
+    AuthBasicProvider socache dbd
+    AuthDBDUserPWQuery "SELECT password FROM authn WHERE user = %s"
+    AuthnCacheProvideFor dbd
+    Require valid-user
+    #Optionnel
+    AuthnCacheContext dbd-authn-example
+</Directory>
    
+
+
    top
    
+
    
+
    La mise en cache avec les modules tiers
    
+    
    Les dveloppeurs de modules doivent savoir que la mise en cache
+    avec mod_authn_socache doit tre active dans leurs modules. La
+    fonction de l'API ap_authn_cache_store permet de
+    mettre en cache les donnes d'authentification qu'un fournisseur
+    vient de rechercher ou de gnrer. Vous trouverez des exemples
+    d'utilisation  r957072, o trois fournisseurs authn sont activs pour la mise
+    en cache.
    
+
    top
    Directive AuthnCacheContext
    
 
    
 
    Description:Specify a context string for use in the cache key
    
 
 
 
 
 
 
    
@@ -184,73 +251,6 @@ utiliser
     dfinissez la dure de vie.
    
-
    top
    
-
    
-
    Mise en cache des donnes d'authentification
    
-    
    Certains utilisateurs qui mettent oeuvre une authentification
-    lourde s'appuyant par exemple sur des requtes SQL
-    (mod_authn_dbd) ont signal une charge induite
-    inacceptable sur leur fournisseur d'authentification. Cela se
-    produit typiquement dans le cas o une page HTML contient des
-    centaines d'objets (images, scripts, pages de styles, media,
-    etc...), et o une requte pour cette page gnre des centaines de
-    sous-requtes  effet immdiat pour des contenus supplmentaires
-    authentifis.
    
-    
    Pour rsoudre ce problme, mod_authn_socache fournit une solution
-    qui permet de maintenir un cache des donnes d'authentification.
    
-
    top
    
-
    
-
    Utilisation
    
-    
    Le cache d'authentification doit tre utilis lorsque les
-    requtes d'authentification induisent une charge significative sur le
-    serveur, le serveur d'arrire-plan ou le rseau. Cette mise en cache
-    n'apportera probablement aucune amlioration dans le cas d'une
-    authentification  base de fichier (mod_authn_file)
-    ou de base de donnes dbm (mod_authn_dbm) car ces
-    mthodes sont de par leur conception rapides et lgres (la mise en
-    cache peut cependant s'avrer utile dans le cas o le fichier est
-    situ sur un montage rseau). Les fournisseurs d'authentification
-    bass sur SQL ou LDAP ont plus de chances de tirer parti de cette
-    mise en cache, en particulier lorsqu'un problme de performances est
-    dtect. mod_authnz_ldap grant son propre cache,
-    seul mod_authn_dbd est concern par notre sujet.
    
-    
    Les principales rgles  appliquer pour la mise en cache sont :
    
-    
    1. Inclure le fournisseur pour lequel vous voulez effectuer une
-    mise en cache dans une directive
-    AuthnCacheProvideFor.
      2. 
-        
    2. Mettre socache avant le fournisseur pour lequel
-	vous voulez effectuer une mise en cache dans votre directive
-	AuthBasicProvider
-	ou AuthDigestProvider.
      3. 
-    
    
-    
    Voici un exemple simple permettant d'acclrer
-    mod_authn_dbd et utilisant dbm comme moteur de la
-    mise en cache :
    
-    
        #AuthnCacheSOCache est optionnel. S'il est dfini, il l'est pour
-    #l'ensemble du serveur
-AuthnCacheSOCache dbm
-<Directory /usr/www/myhost/private>
-    AuthType Basic
-    AuthName "Cached Authentication Example"
-    AuthBasicProvider socache dbd
-    AuthDBDUserPWQuery "SELECT password FROM authn WHERE user = %s"
-    AuthnCacheProvideFor dbd
-    Require valid-user
-    #Optionnel
-    AuthnCacheContext dbd-authn-example
-</Directory>
    
-
-
    top
    
-
    
-
    La mise en cache avec les modules tiers
    
-    
    Les dveloppeurs de modules doivent savoir que la mise en cache
-    avec mod_authn_socache doit tre active dans leurs modules. La
-    fonction de l'API ap_authn_cache_store permet de
-    mettre en cache les donnes d'authentification qu'un fournisseur
-    vient de rechercher ou de gnrer. Vous trouverez des exemples
-    d'utilisation  r957072, o trois fournisseurs authn sont activs pour la mise
-    en cache.
    
-
    
 
    Langues Disponibles:  en  |
diff --git a/docs/manual/mod/mod_authn_socache.xml b/docs/manual/mod/mod_authn_socache.xml
index b5d3254f72..e371841388 100644
--- a/docs/manual/mod/mod_authn_socache.xml
+++ b/docs/manual/mod/mod_authn_socache.xml
@@ -72,7 +72,7 @@ the load on backends
     
 #AuthnCacheSOCache is optional.  If specified, it is server-wide
 AuthnCacheSOCache dbm
-<Directory /usr/www/myhost/private>
+<Directory "/usr/www/myhost/private">
     AuthType Basic
     AuthName "Cached Authentication Example"
     AuthBasicProvider socache dbd
diff --git a/docs/manual/mod/mod_authnz_fcgi.html.en b/docs/manual/mod/mod_authnz_fcgi.html.en
index 55e3a674ff..398d8129b8 100644
--- a/docs/manual/mod/mod_authnz_fcgi.html.en
+++ b/docs/manual/mod/mod_authnz_fcgi.html.en
@@ -65,127 +65,6 @@ and Access Control
 
  • mod_proxy_fcgi
    • 
 
    top
    
-
    AuthnzFcgiCheckAuthnProvider Directive
    
-
    
 
 
 
 
 
    
-
-
-
-
-
-
-
    Description:Enables a FastCGI application to handle the check_authn
-authentication hook.
    Syntax:AuthnzFcgiCheckAuthnProvider provider-name|None
-option ...
    Default:none
    Context:directory
    Status:Extension
    Module:mod_authnz_fcgi
    
-    
    This directive is used to enable a FastCGI authorizer to
-    handle a specific processing phase of authentication or
-    authorization.
    
-
-    
    Some capabilities of FastCGI authorizers require enablement
-    using this directive instead of
-    AuthBasicProvider:
    
-
-    
      
-      
    • Non-Basic authentication; generally, determining the user
-      id of the client and returning it from the authorizer; see the
-      UserExpr option below
      • 
-      
    • Selecting a custom response code; for a non-200 response
-      from the authorizer, the code from the authorizer will be the
-      status of the response
      • 
-      
    • Setting the body of a non-200 response; if the authorizer
-      provides a response body with a non-200 response, that body
-      will be returned to the client; up to 8192 bytes of text are
-      supported
      • 
-    
    
-
-    
    
-      
    provider-name
    
-      
    This is the name of a provider defined with 
-      AuthnzFcgiDefineProvider.
    
-
-      
    None
    
-      
    Specify None to disable a provider enabled
-      with this directive in an outer scope, such as in a parent
-      directory.
    
-
-      
    option
    
-      
    The following options are supported:
-      
-      
    
-         
    Authoritative On|Off (default On)
    
-         
    This controls whether or not other modules are allowed
-         to run when this module has a FastCGI authorizer configured
-         and it fails the request.
    
-
-         
    DefaultUser userid
    
-         
    When the authorizer returns success and UserExpr
-         is configured and evaluates to an empty string (e.g., authorizer
-         didn't return a variable), this value will be used as the user
-         id.  This is typically used when the authorizer has a concept of
-         guest, or unauthenticated, users and guest users are mapped to
-         some specific user id for logging and other purposes.
    
-
-         
    RequireBasicAuth On|Off (default Off)
    
-         
    This controls whether or not Basic auth is required
-         before passing the request to the authorizer.  If required,
-         the authorizer won't be invoked without a user id and
-         password; 401 will be returned for a request without that.
    
-
-         
    UserExpr expr (no default)
    
-         
    When Basic authentication isn't provided by the client
-         and the authorizer determines the user, this expression,
-         evaluated after calling the authorizer, determines the
-         user.  The expression follows 
-         ap_expr syntax and must resolve to a string.  A typical
-         use is to reference a Variable-XXX 
-         setting returned by the authorizer using an option like
-         UserExpr "%{reqenv:XXX}".  If
-         this option is specified and the user id can't be retrieved
-         using the expression after a successful authentication, the
-         request will be rejected with a 500 error.
    
-
-       
    
-      
    
-     
    
-
-
    
-
    top
    
-
    AuthnzFcgiDefineProvider Directive
    
-
-
-
-
-
-
-
-
    Description:Defines a FastCGI application as a provider for
-authentication and/or authorization
    Syntax:AuthnzFcgiDefineProvider type provider-name
-backend-address
    Default:none
    Context:server config
    Status:Extension
    Module:mod_authnz_fcgi
    
-    
    This directive is used to define a FastCGI application as
-    a provider for a particular phase of authentication or
-    authorization.
    
-
-    
    
-      
    type
    
-      
    This must be set to authn for authentication,
-      authz for authorization, or authnz for
-      a generic FastCGI authorizer which performs both checks.
    
-
-      
    provider-name
    
-      
    This is used to assign a name to the provider which is
-      used in other directives such as 
-      AuthBasicProvider
-      and 
-      Require.
    
-
-      
    backend-address
    
-      
    This specifies the address of the application, in the form
-      fcgi://hostname:port/.  The application process(es)
-      must be managed independently, such as with
-      fcgistarter.
    
-    
    
-
-
    
-
    top
    
 
    
 
    Invocation modes
    
 
@@ -246,7 +125,7 @@ while (FCGI::accept >= 0) {
 
       Example configuration:
 
    AuthnzFcgiDefineProvider authn FooAuthn fcgi://localhost:10102/
-<Location /protected/>
+<Location "/protected/">
   AuthType Basic
   AuthName "Restricted"
   AuthBasicProvider FooAuthn
@@ -287,7 +166,7 @@ while (FCGI::accept >= 0) {
 
       Example configuration:
 
    AuthnzFcgiDefineProvider authz FooAuthz fcgi://localhost:10103/
-<Location /protected/>
+<Location "/protected/">
   AuthType ...
   AuthName ...
   AuthBasicProvider ...
@@ -338,7 +217,7 @@ while (FCGI::accept >= 0) {
 
       Example configuration:
 
    AuthnzFcgiDefineProvider authnz FooAuthnz fcgi://localhost:10103/
-<Location /protected/>
+<Location "/protected/">
   AuthType Basic
   AuthName "Restricted"
   AuthBasicProvider FooAuthnz
@@ -386,7 +265,7 @@ while (FCGI::accept >= 0) {
 
       Example configuration:
 
    AuthnzFcgiDefineProvider authn FooAuthn fcgi://localhost:10103/
-<Location /protected/>
+<Location "/protected/">
   AuthType ...
   AuthName ...
   AuthnzFcgiCheckAuthnProvider FooAuthn \
@@ -527,6 +406,127 @@ Require FooAuthnz
    
 
    LogLevel info authnz_fcgi:trace8
    
 
 
+
    
+
    top
    
+
    AuthnzFcgiCheckAuthnProvider Directive
    
+
+
+
+
+
+
+
+
    Description:Enables a FastCGI application to handle the check_authn
+authentication hook.
    Syntax:AuthnzFcgiCheckAuthnProvider provider-name|None
+option ...
    Default:none
    Context:directory
    Status:Extension
    Module:mod_authnz_fcgi
    
+    
    This directive is used to enable a FastCGI authorizer to
+    handle a specific processing phase of authentication or
+    authorization.
    
+
+    
    Some capabilities of FastCGI authorizers require enablement
+    using this directive instead of
+    AuthBasicProvider:
    
+
+    
      
+      
    • Non-Basic authentication; generally, determining the user
+      id of the client and returning it from the authorizer; see the
+      UserExpr option below
      • 
+      
    • Selecting a custom response code; for a non-200 response
+      from the authorizer, the code from the authorizer will be the
+      status of the response
      • 
+      
    • Setting the body of a non-200 response; if the authorizer
+      provides a response body with a non-200 response, that body
+      will be returned to the client; up to 8192 bytes of text are
+      supported
      • 
+    
    
+
+    
    
+      
    provider-name
    
+      
    This is the name of a provider defined with 
+      AuthnzFcgiDefineProvider.
    
+
+      
    None
    
+      
    Specify None to disable a provider enabled
+      with this directive in an outer scope, such as in a parent
+      directory.
    
+
+      
    option
    
+      
    The following options are supported:
+      
+      
    
+         
    Authoritative On|Off (default On)
    
+         
    This controls whether or not other modules are allowed
+         to run when this module has a FastCGI authorizer configured
+         and it fails the request.
    
+
+         
    DefaultUser userid
    
+         
    When the authorizer returns success and UserExpr
+         is configured and evaluates to an empty string (e.g., authorizer
+         didn't return a variable), this value will be used as the user
+         id.  This is typically used when the authorizer has a concept of
+         guest, or unauthenticated, users and guest users are mapped to
+         some specific user id for logging and other purposes.
    
+
+         
    RequireBasicAuth On|Off (default Off)
    
+         
    This controls whether or not Basic auth is required
+         before passing the request to the authorizer.  If required,
+         the authorizer won't be invoked without a user id and
+         password; 401 will be returned for a request without that.
    
+
+         
    UserExpr expr (no default)
    
+         
    When Basic authentication isn't provided by the client
+         and the authorizer determines the user, this expression,
+         evaluated after calling the authorizer, determines the
+         user.  The expression follows 
+         ap_expr syntax and must resolve to a string.  A typical
+         use is to reference a Variable-XXX 
+         setting returned by the authorizer using an option like
+         UserExpr "%{reqenv:XXX}".  If
+         this option is specified and the user id can't be retrieved
+         using the expression after a successful authentication, the
+         request will be rejected with a 500 error.
    
+
+       
    
+      
    
+     
    
+
+
    
+
    top
    
+
    AuthnzFcgiDefineProvider Directive
    
+
+
+
+
+
+
+
+
    Description:Defines a FastCGI application as a provider for
+authentication and/or authorization
    Syntax:AuthnzFcgiDefineProvider type provider-name
+backend-address
    Default:none
    Context:server config
    Status:Extension
    Module:mod_authnz_fcgi
    
+    
    This directive is used to define a FastCGI application as
+    a provider for a particular phase of authentication or
+    authorization.
    
+
+    
    
+      
    type
    
+      
    This must be set to authn for authentication,
+      authz for authorization, or authnz for
+      a generic FastCGI authorizer which performs both checks.
    
+
+      
    provider-name
    
+      
    This is used to assign a name to the provider which is
+      used in other directives such as 
+      AuthBasicProvider
+      and 
+      Require.
    
+
+      
    backend-address
    
+      
    This specifies the address of the application, in the form
+      fcgi://hostname:port/.  The application process(es)
+      must be managed independently, such as with
+      fcgistarter.
    
+    
    
+
 
    
 
 
    
diff --git a/docs/manual/mod/mod_authnz_fcgi.xml b/docs/manual/mod/mod_authnz_fcgi.xml
index 5cefa686e9..8430e6feb7 100644
--- a/docs/manual/mod/mod_authnz_fcgi.xml
+++ b/docs/manual/mod/mod_authnz_fcgi.xml
@@ -110,7 +110,7 @@ while (FCGI::accept >= 0) {
       Example configuration:
 
 AuthnzFcgiDefineProvider authn FooAuthn fcgi://localhost:10102/
-<Location /protected/>
+<Location "/protected/">
   AuthType Basic
   AuthName "Restricted"
   AuthBasicProvider FooAuthn
@@ -153,7 +153,7 @@ while (FCGI::accept >= 0) {
       Example configuration:
 
 AuthnzFcgiDefineProvider authz FooAuthz fcgi://localhost:10103/
-<Location /protected/>
+<Location "/protected/">
   AuthType ...
   AuthName ...
   AuthBasicProvider ...
@@ -206,7 +206,7 @@ while (FCGI::accept >= 0) {
       Example configuration:
 
 AuthnzFcgiDefineProvider authnz FooAuthnz fcgi://localhost:10103/
-<Location /protected/>
+<Location "/protected/">
   AuthType Basic
   AuthName "Restricted"
   AuthBasicProvider FooAuthnz
@@ -257,7 +257,7 @@ while (FCGI::accept >= 0) {
       Example configuration:
 
 AuthnzFcgiDefineProvider authn FooAuthn fcgi://localhost:10103/
-<Location /protected/>
+<Location "/protected/">
   AuthType ...
   AuthName ...
   AuthnzFcgiCheckAuthnProvider FooAuthn \
diff --git a/docs/manual/mod/mod_authnz_ldap.html.en b/docs/manual/mod/mod_authnz_ldap.html.en
index a371fd83ee..465ec9b022 100644
--- a/docs/manual/mod/mod_authnz_ldap.html.en
+++ b/docs/manual/mod/mod_authnz_ldap.html.en
@@ -101,620 +101,6 @@ for HTTP Basic authentication.
    
 
 
 
    
-
-
-
-
-
-
-
-
-
    Description:Specifies the prefix for environment variables set during
-authorization
    Syntax:AuthLDAPAuthorizePrefix prefix
    Default:AuthLDAPAuthorizePrefix AUTHORIZE_
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.6 and later
    
-    
    This directive allows you to override the prefix used for environment
-    variables set during LDAP authorization.  If AUTHENTICATE_ is
-    specified, consumers of these environment variables see the same information
-    whether LDAP has performed authentication, authorization, or both.
    
-
-    
    Note
    
-    No authorization variables are set when a user is authorized on the basis of
-    Require valid-user.
-    
    
-
-
    
-
    top
    
-
    AuthLDAPBindAuthoritative Directive
    
-
-
-
-
-
-
-
-
-
    Description:Determines if other authentication providers are used when a user can be mapped to a DN but the server cannot successfully bind with the user's credentials.
    Syntax:AuthLDAPBindAuthoritativeoff|on
    Default:AuthLDAPBindAuthoritative on
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
-    
    By default, subsequent authentication providers are only queried if a
-    user cannot be mapped to a DN, but not if the user can be mapped to a DN and their
-    password cannot be verified with an LDAP bind.
-    If AuthLDAPBindAuthoritative
-    is set to off, other configured authentication modules will have
-    a chance to validate the user if the LDAP bind (with the current user's credentials)
-    fails for any reason.
    
-    
     This allows users present in both LDAP and
-    AuthUserFile to authenticate
-    when the LDAP server is available but the user's account is locked or password
-    is otherwise unusable.
    
-
-
    See also
    
-
-
    
-
    top
    
-
    AuthLDAPBindDN Directive
    
-
-
-
-
-
-
-
-
    Description:Optional DN to use in binding to the LDAP server
    Syntax:AuthLDAPBindDN distinguished-name
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
-    
    An optional DN used to bind to the server when searching for
-    entries. If not provided, mod_authnz_ldap will use
-    an anonymous bind.
    
-
-
    
-
    top
    
-
    AuthLDAPBindPassword Directive
    
-
-
-
-
-
-
-
-
-
    Description:Password used in conjuction with the bind DN
    Syntax:AuthLDAPBindPassword password
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:exec: was added in 2.4.5.
    
-    
    A bind password to use in conjunction with the bind DN. Note
-    that the bind password is probably sensitive data, and should be
-    properly protected. You should only use the AuthLDAPBindDN and AuthLDAPBindPassword if you
-    absolutely need them to search the directory.
    
-
-    
    If the value begins with exec: the resulting command will be
-    executed and the first line returned to standard output by the
-    program will be used as the password.
    
-
    #Password used as-is
-AuthLDAPBindPassword secret
-
-#Run /path/to/program to get my password
-AuthLDAPBindPassword exec:/path/to/program
-
-#Run /path/to/otherProgram and provide arguments
-AuthLDAPBindPassword "exec:/path/to/otherProgram argument1"
    
-
-
-
-
    
-
    top
    
-
    AuthLDAPCharsetConfig Directive
    
-
-
-
-
-
-
-
    Description:Language to charset conversion configuration file
    Syntax:AuthLDAPCharsetConfig file-path
    Context:server config
    Status:Extension
    Module:mod_authnz_ldap
    
-    
    The AuthLDAPCharsetConfig directive sets the location
-    of the language to charset conversion configuration file. File-path is relative
-    to the ServerRoot. This file specifies
-    the list of language extensions to character sets.
-    Most administrators use the provided charset.conv
-    file, which associates common language extensions to character sets.
    
-
-    
    The file contains lines in the following format:
    
-
-    
    
-      Language-Extension charset [Language-String] ...
-    
    
-
-    
    The case of the extension does not matter. Blank lines, and lines
-    beginning with a hash character (#) are ignored.
    
-
-
    
-
    top
    
-
    AuthLDAPCompareAsUser Directive
    
-
-
-
-
-
-
-
-
-
-
    Description:Use the authenticated user's credentials to perform authorization comparisons
    Syntax:AuthLDAPCompareAsUser on|off
    Default:AuthLDAPCompareAsUser off
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.6 and later
    
-    
    When set, and mod_authnz_ldap has authenticated the
-    user, LDAP comparisons for authorization use the queried distinguished name (DN)
-    and HTTP basic authentication password of the authenticated user instead of
-    the servers configured credentials.
    
-
-    
     The ldap-attribute, ldap-user, and ldap-group (single-level only)
-    authorization checks use comparisons.
    
-
-    
    This directive only has effect on the comparisons performed during
-    nested group processing when 
-    AuthLDAPSearchAsUser is also enabled.
    
-
-    
     This directive should only be used when your LDAP server doesn't
-        accept anonymous comparisons and you cannot use a dedicated
-        AuthLDAPBindDN.
-    
    
-
-
    See also
    
-
-
    
-
    top
    
-
    AuthLDAPCompareDNOnServer Directive
    
-
-
-
-
-
-
-
-
-
    Description:Use the LDAP server to compare the DNs
    Syntax:AuthLDAPCompareDNOnServer on|off
    Default:AuthLDAPCompareDNOnServer on
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
-    
    When set, mod_authnz_ldap will use the LDAP
-    server to compare the DNs. This is the only foolproof way to
-    compare DNs.  mod_authnz_ldap will search the
-    directory for the DN specified with the Require dn directive, then,
-    retrieve the DN and compare it with the DN retrieved from the user
-    entry. If this directive is not set,
-    mod_authnz_ldap simply does a string comparison. It
-    is possible to get false negatives with this approach, but it is
-    much faster. Note the mod_ldap cache can speed up
-    DN comparison in most situations.
    
-
-
    
-
    top
    
-
    AuthLDAPDereferenceAliases Directive
    
-
-
-
-
-
-
-
-
-
    Description:When will the module de-reference aliases
    Syntax:AuthLDAPDereferenceAliases never|searching|finding|always
    Default:AuthLDAPDereferenceAliases always
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
-    
    This directive specifies when mod_authnz_ldap will
-    de-reference aliases during LDAP operations. The default is
-    always.
    
-
-
    
-
    top
    
-
    AuthLDAPGroupAttribute Directive
    
-
-
-
-
-
-
-
-
-
    Description:LDAP attributes used to identify the user members of
-groups.
    Syntax:AuthLDAPGroupAttribute attribute
    Default:AuthLDAPGroupAttribute member uniquemember
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
-    
    This directive specifies which LDAP attributes are used to
-    check for user members within groups. Multiple attributes can be used
-    by specifying this directive multiple times. If not specified,
-    then mod_authnz_ldap uses the member and
-    uniquemember attributes.
    
-
-
    
-
    top
    
-
    AuthLDAPGroupAttributeIsDN Directive
    
-
-
-
-
-
-
-
-
-
    Description:Use the DN of the client username when checking for
-group membership
    Syntax:AuthLDAPGroupAttributeIsDN on|off
    Default:AuthLDAPGroupAttributeIsDN on
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
-    
    When set on, this directive says to use the
-    distinguished name of the client username when checking for group
-    membership.  Otherwise, the username will be used. For example,
-    assume that the client sent the username bjenson,
-    which corresponds to the LDAP DN cn=Babs Jenson,
-    o=Example. If this directive is set,
-    mod_authnz_ldap will check if the group has
-    cn=Babs Jenson, o=Example as a member. If this
-    directive is not set, then mod_authnz_ldap will
-    check if the group has bjenson as a member.
    
-
-
    
-
    top
    
-
    AuthLDAPInitialBindAsUser Directive
    
-
-
-
-
-
-
-
-
-
-
    Description:Determines if the server does the initial DN lookup using the basic authentication users'
-own username, instead of anonymously or with hard-coded credentials for the server
    Syntax:AuthLDAPInitialBindAsUser off|on
    Default:AuthLDAPInitialBindAsUser off
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.6 and later
    
-    
    By default, the server either anonymously, or with a dedicated user and
-     password, converts the basic authentication username into an LDAP
-     distinguished name (DN).  This directive forces the server to use the verbatim username
-     and password provided by the incoming user to perform the initial DN
-     search.
    
-
-     
     If the verbatim username can't directly bind, but needs some
-     cosmetic transformation, see 
-     AuthLDAPInitialBindPattern.
    
-
-     
     This directive should only be used when your LDAP server doesn't
-         accept anonymous searches and you cannot use a dedicated
-         AuthLDAPBindDN.
-     
    
-
-     
    Not available with authorization-only
    
-         This directive can only be used if this module authenticates the user, and
-         has no effect when this module is used exclusively for authorization.
-     
    
-
-
    See also
    
-
-
    
-
    top
    
-
    AuthLDAPInitialBindPattern Directive
    
-
-
-
-
-
-
-
-
-
-
    Description:Specifies the transformation of the basic authentication username to be used when binding to the LDAP server
-to perform a DN lookup
    Syntax:AuthLDAPInitialBindPatternregex substitution
    Default:AuthLDAPInitialBindPattern (.*) $1 (remote username used verbatim)
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.6 and later
    
-    
    If AuthLDAPInitialBindAsUser is set to
-       ON, the basic authentication username will be transformed according to the
-       regular expression and substituion arguments.
    
-
-    
     The regular expression argument is compared against the current basic authentication username.
-        The substitution argument may contain backreferences, but has no other variable interpolation.
    
-
-    
     This directive should only be used when your LDAP server doesn't
-        accept anonymous searches and you cannot use a dedicated
-        AuthLDAPBindDN.
-    
    
-
-    
    AuthLDAPInitialBindPattern (.+) $1@example.com
    
-
-    
    AuthLDAPInitialBindPattern (.+) cn=$1,dc=example,dc=com
    
-
-
-    
    Not available with authorization-only
    
-        This directive can only be used if this module authenticates the user, and
-        has no effect when this module is used exclusively for authorization.
-    
    
-    
    debugging
    
-        The substituted DN is recorded in the environment variable
-        LDAP_BINDASUSER.  If the regular expression does not match the input,
-        the verbatim username is used.
-    
    
-
-
    See also
    
-
-
    
-
    top
    
-
    AuthLDAPMaxSubGroupDepth Directive
    
-
-
-
-
-
-
-
-
-
-
    Description:Specifies the maximum sub-group nesting depth that will be
-evaluated before the user search is discontinued.
    Syntax:AuthLDAPMaxSubGroupDepth Number
    Default:AuthLDAPMaxSubGroupDepth 0
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.0 and later, defaulted to 10 in 2.4.x and early 2.5
    
-   
    When this directive is set to a non-zero value X
-   combined with use of the Require ldap-group someGroupDN
-   directive, the provided user credentials will be searched for
-   as a member of the someGroupDN directory object or of
-   any group member of the current group up to the maximum nesting
-   level X specified by this directive.
    
-   
    See the Require ldap-group
-   section for a more detailed example.
    
-
-   
    Nested groups performance
    
-   
     When AuthLDAPSubGroupAttribute overlaps with
-   AuthLDAPGroupAttribute (as it does by default and
-   as required by common LDAP schemas), uncached searching for subgroups in 
-   large groups can be very slow. If you use large, non-nested groups, keep 
-   AuthLDAPMaxSubGroupDepth set to zero.
    
-   
    
-
-
-
    
-
    top
    
-
    AuthLDAPRemoteUserAttribute Directive
    
-
-
-
-
-
-
-
-
-
    Description:Use the value of the attribute returned during the user
-query to set the REMOTE_USER environment variable
    Syntax:AuthLDAPRemoteUserAttribute uid
    Default:none
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
-    
    If this directive is set, the value of the
-    REMOTE_USER environment variable will be set to the
-    value of the attribute specified. Make sure that this attribute is
-    included in the list of attributes in the AuthLDAPUrl definition,
-    otherwise this directive will have no effect. This directive, if
-    present, takes precedence over AuthLDAPRemoteUserIsDN. This
-    directive is useful should you want people to log into a website
-    using an email address, but a backend application expects the
-    username as a userid.
    
-    
     This directive only has effect when this module is used for 
-    authentication.
    
-
-
    
-
    top
    
-
    AuthLDAPRemoteUserIsDN Directive
    
-
-
-
-
-
-
-
-
-
    Description:Use the DN of the client username to set the REMOTE_USER
-environment variable
    Syntax:AuthLDAPRemoteUserIsDN on|off
    Default:AuthLDAPRemoteUserIsDN off
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
-    
    If this directive is set to on, the value of the
-    REMOTE_USER environment variable will be set to the full
-    distinguished name of the authenticated user, rather than just
-    the username that was passed by the client. It is turned off by
-    default.
    
-    
     This directive only has effect when this module is used for
-    authentication.
    
-
-
    
-
    top
    
-
    AuthLDAPSearchAsUser Directive
    
-
-
-
-
-
-
-
-
-
-
    Description:Use the authenticated user's credentials to perform authorization searches
    Syntax:AuthLDAPSearchAsUser on|off
    Default:AuthLDAPSearchAsUser off
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.6 and later
    
-    
    When set, and mod_authnz_ldap has authenticated the
-    user, LDAP searches for authorization use the queried distinguished name (DN)
-    and HTTP basic authentication password of the authenticated user instead of
-    the servers configured credentials.
    
-
-    
     The ldap-filter and ldap-dn authorization
-    checks use searches.
    
-
-    
    This directive only has effect on the comparisons performed during
-    nested group processing when 
-    AuthLDAPCompareAsUser is also enabled.
    
-
-    
     This directive should only be used when your LDAP server doesn't
-        accept anonymous searches and you cannot use a dedicated
-        AuthLDAPBindDN.
-    
    
-
-
    See also
    
-
-
    
-
    top
    
-
    AuthLDAPSubGroupAttribute Directive
    
-
-
-
-
-
-
-
-
-
-
    Description:Specifies the attribute labels, one value per
-directive line, used to distinguish the members of the current group that
-are groups.
    Syntax:AuthLDAPSubGroupAttribute attribute
    Default:AuthLDAPSubgroupAttribute member uniquemember
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.0 and later
    
-    
    An LDAP group object may contain members that are users and
-    members that are groups (called nested or sub groups). The
-    AuthLDAPSubGroupAttribute directive identifies the
-    labels of group members and the AuthLDAPGroupAttribute
-    directive identifies the labels of the user members. Multiple
-    attributes can be used by specifying this directive multiple times.
-    If not specified, then mod_authnz_ldap uses the
-    member and uniqueMember attributes.
    
-
-
    
-
    top
    
-
    AuthLDAPSubGroupClass Directive
    
-
-
-
-
-
-
-
-
-
-
    Description:Specifies which LDAP objectClass values identify directory
-objects that are groups during sub-group processing.
    Syntax:AuthLDAPSubGroupClass LdapObjectClass
    Default:AuthLDAPSubGroupClass groupOfNames groupOfUniqueNames
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.0 and later
    
-    
    An LDAP group object may contain members that are users and
-    members that are groups (called nested or sub groups). The
-    AuthLDAPSubGroupAttribute directive identifies the
-    labels of members that may be sub-groups of the current group
-    (as opposed to user members). The AuthLDAPSubGroupClass
-    directive specifies the LDAP objectClass values used in verifying that
-    these potential sub-groups are in fact group objects. Verified sub-groups
-    can then be searched for more user or sub-group members. Multiple
-    attributes can be used by specifying this directive multiple times.
-    If not specified, then mod_authnz_ldap uses the
-    groupOfNames and groupOfUniqueNames values.
    
-
-
    
-
    top
    
-
    AuthLDAPUrl Directive
    
-
-
-
-
-
-
-
-
    Description:URL specifying the LDAP search parameters
    Syntax:AuthLDAPUrl url [NONE|SSL|TLS|STARTTLS]
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
-    
    An RFC 2255 URL which specifies the LDAP search parameters
-    to use. The syntax of the URL is
    
-
    ldap://host:port/basedn?attribute?scope?filter
    
-    
    If you want to specify more than one LDAP URL that Apache should try in turn, the syntax is:
    
-
    AuthLDAPUrl "ldap://ldap1.example.com ldap2.example.com/dc=..."
    
-
-
    Caveat: If you specify multiple servers, you need to enclose the entire URL string in quotes;
-otherwise you will get an error: "AuthLDAPURL takes one argument, URL to define LDAP connection.." 
-You can of course use search parameters on each of these.
    
-
-
    
-
    ldap
    
-
-        
    For regular ldap, use the
-        string ldap. For secure LDAP, use ldaps
-        instead. Secure LDAP is only available if Apache was linked
-        to an LDAP library with SSL support.
    
-
-
    host:port
    
-
-        
    
-          
    The name/port of the ldap server (defaults to
-          localhost:389 for ldap, and
-          localhost:636 for ldaps). To
-          specify multiple, redundant LDAP servers, just list all
-          servers, separated by spaces. mod_authnz_ldap
-          will try connecting to each server in turn, until it makes a
-          successful connection. If multiple ldap servers are specified,
-          then entire LDAP URL must be encapsulated in double quotes.
    
-
-          
    Once a connection has been made to a server, that
-          connection remains active for the life of the
-          httpd process, or until the LDAP server goes
-          down.
    
-
-          
    If the LDAP server goes down and breaks an existing
-          connection, mod_authnz_ldap will attempt to
-          re-connect, starting with the primary server, and trying
-          each redundant server in turn. Note that this is different
-          than a true round-robin search.
    
-        
    
-
-
    basedn
    
-
-        
    The DN of the branch of the
-        directory where all searches should start from. At the very
-        least, this must be the top of your directory tree, but
-        could also specify a subtree in the directory.
    
-
-
    attribute
    
-
-        
    The attribute to search for.
-        Although RFC 2255 allows a comma-separated list of
-        attributes, only the first attribute will be used, no
-        matter how many are provided. If no attributes are
-        provided, the default is to use uid. It's a good
-        idea to choose an attribute that will be unique across all
-        entries in the subtree you will be using.  All attributes
-        listed will be put into the environment with an AUTHENTICATE_ prefix
-        for use by other modules.
    
-
-
    scope
    
-
-        
    The scope of the search. Can be either one or
-        sub. Note that a scope of base is
-        also supported by RFC 2255, but is not supported by this
-        module. If the scope is not provided, or if base scope
-        is specified, the default is to use a scope of
-        sub.
    
-
-
    filter
    
-
-        
    A valid LDAP search filter. If
-        not provided, defaults to (objectClass=*), which
-        will search for all objects in the tree. Filters are
-        limited to approximately 8000 characters (the definition of
-        MAX_STRING_LEN in the Apache source code). This
-        should be more than sufficient for any application. The keyword
-        none disables the use of a filter; this is required
-        by some primitive LDAP servers.
    
-
    
-
-    
    When doing searches, the attribute, filter and username passed
-    by the HTTP client are combined to create a search filter that
-    looks like
-    (&(filter)(attribute=username)).
    
-
-    
    For example, consider an URL of
-    ldap://ldap.example.com/o=Example?cn?sub?(posixid=*). When
-    a client attempts to connect using a username of Babs
-    Jenson, the resulting search filter will be
-    (&(posixid=*)(cn=Babs Jenson)).
    
-
-    
    An optional parameter can be added to allow the LDAP Url to override
-    the connection type.  This parameter can be one of the following:
    
-
-
    
-    
    NONE
    
-        
    Establish an unsecure connection on the default LDAP port. This
-        is the same as ldap:// on port 389.
    
-    
    SSL
    
-        
    Establish a secure connection on the default secure LDAP port.
-        This is the same as ldaps://
    
-    
    TLS | STARTTLS
    
-        
    Establish an upgraded secure connection on the default LDAP port.
-        This connection will be initiated on port 389 by default and then
-        upgraded to a secure connection on the same port.
    
-
    
-
-    
    See above for examples of AuthLDAPURL URLs.
    
-
-
    
-
    top
    
 
    
 
    Contents
    
 
@@ -1419,6 +805,620 @@ Require group     mygroupfile
       and won't be able to find the FrontPage-managed user file.
     
 
+
    
+
    top
    
+
    AuthLDAPAuthorizePrefix Directive
    
+
+
+
+
+
+
+
+
+
+
    Description:Specifies the prefix for environment variables set during
+authorization
    Syntax:AuthLDAPAuthorizePrefix prefix
    Default:AuthLDAPAuthorizePrefix AUTHORIZE_
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.6 and later
    
+    
    This directive allows you to override the prefix used for environment
+    variables set during LDAP authorization.  If AUTHENTICATE_ is
+    specified, consumers of these environment variables see the same information
+    whether LDAP has performed authentication, authorization, or both.
    
+
+    
    Note
    
+    No authorization variables are set when a user is authorized on the basis of
+    Require valid-user.
+    
    
+
+
    
+
    top
    
+
    AuthLDAPBindAuthoritative Directive
    
+
+
+
+
+
+
+
+
+
    Description:Determines if other authentication providers are used when a user can be mapped to a DN but the server cannot successfully bind with the user's credentials.
    Syntax:AuthLDAPBindAuthoritativeoff|on
    Default:AuthLDAPBindAuthoritative on
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
+    
    By default, subsequent authentication providers are only queried if a
+    user cannot be mapped to a DN, but not if the user can be mapped to a DN and their
+    password cannot be verified with an LDAP bind.
+    If AuthLDAPBindAuthoritative
+    is set to off, other configured authentication modules will have
+    a chance to validate the user if the LDAP bind (with the current user's credentials)
+    fails for any reason.
    
+    
     This allows users present in both LDAP and
+    AuthUserFile to authenticate
+    when the LDAP server is available but the user's account is locked or password
+    is otherwise unusable.
    
+
+
    See also
    
+
+
    
+
    top
    
+
    AuthLDAPBindDN Directive
    
+
+
+
+
+
+
+
+
    Description:Optional DN to use in binding to the LDAP server
    Syntax:AuthLDAPBindDN distinguished-name
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
+    
    An optional DN used to bind to the server when searching for
+    entries. If not provided, mod_authnz_ldap will use
+    an anonymous bind.
    
+
+
    
+
    top
    
+
    AuthLDAPBindPassword Directive
    
+
+
+
+
+
+
+
+
+
    Description:Password used in conjuction with the bind DN
    Syntax:AuthLDAPBindPassword password
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:exec: was added in 2.4.5.
    
+    
    A bind password to use in conjunction with the bind DN. Note
+    that the bind password is probably sensitive data, and should be
+    properly protected. You should only use the AuthLDAPBindDN and AuthLDAPBindPassword if you
+    absolutely need them to search the directory.
    
+
+    
    If the value begins with exec: the resulting command will be
+    executed and the first line returned to standard output by the
+    program will be used as the password.
    
+
    #Password used as-is
+AuthLDAPBindPassword secret
+
+#Run /path/to/program to get my password
+AuthLDAPBindPassword exec:/path/to/program
+
+#Run /path/to/otherProgram and provide arguments
+AuthLDAPBindPassword "exec:/path/to/otherProgram argument1"
    
+
+
+
+
    
+
    top
    
+
    AuthLDAPCharsetConfig Directive
    
+
+
+
+
+
+
+
    Description:Language to charset conversion configuration file
    Syntax:AuthLDAPCharsetConfig file-path
    Context:server config
    Status:Extension
    Module:mod_authnz_ldap
    
+    
    The AuthLDAPCharsetConfig directive sets the location
+    of the language to charset conversion configuration file. File-path is relative
+    to the ServerRoot. This file specifies
+    the list of language extensions to character sets.
+    Most administrators use the provided charset.conv
+    file, which associates common language extensions to character sets.
    
+
+    
    The file contains lines in the following format:
    
+
+    
    
+      Language-Extension charset [Language-String] ...
+    
    
+
+    
    The case of the extension does not matter. Blank lines, and lines
+    beginning with a hash character (#) are ignored.
    
+
+
    
+
    top
    
+
    AuthLDAPCompareAsUser Directive
    
+
+
+
+
+
+
+
+
+
+
    Description:Use the authenticated user's credentials to perform authorization comparisons
    Syntax:AuthLDAPCompareAsUser on|off
    Default:AuthLDAPCompareAsUser off
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.6 and later
    
+    
    When set, and mod_authnz_ldap has authenticated the
+    user, LDAP comparisons for authorization use the queried distinguished name (DN)
+    and HTTP basic authentication password of the authenticated user instead of
+    the servers configured credentials.
    
+
+    
     The ldap-attribute, ldap-user, and ldap-group (single-level only)
+    authorization checks use comparisons.
    
+
+    
    This directive only has effect on the comparisons performed during
+    nested group processing when 
+    AuthLDAPSearchAsUser is also enabled.
    
+
+    
     This directive should only be used when your LDAP server doesn't
+        accept anonymous comparisons and you cannot use a dedicated
+        AuthLDAPBindDN.
+    
    
+
+
    See also
    
+
+
    
+
    top
    
+
    AuthLDAPCompareDNOnServer Directive
    
+
+
+
+
+
+
+
+
+
    Description:Use the LDAP server to compare the DNs
    Syntax:AuthLDAPCompareDNOnServer on|off
    Default:AuthLDAPCompareDNOnServer on
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
+    
    When set, mod_authnz_ldap will use the LDAP
+    server to compare the DNs. This is the only foolproof way to
+    compare DNs.  mod_authnz_ldap will search the
+    directory for the DN specified with the Require dn directive, then,
+    retrieve the DN and compare it with the DN retrieved from the user
+    entry. If this directive is not set,
+    mod_authnz_ldap simply does a string comparison. It
+    is possible to get false negatives with this approach, but it is
+    much faster. Note the mod_ldap cache can speed up
+    DN comparison in most situations.
    
+
+
    
+
    top
    
+
    AuthLDAPDereferenceAliases Directive
    
+
+
+
+
+
+
+
+
+
    Description:When will the module de-reference aliases
    Syntax:AuthLDAPDereferenceAliases never|searching|finding|always
    Default:AuthLDAPDereferenceAliases always
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
+    
    This directive specifies when mod_authnz_ldap will
+    de-reference aliases during LDAP operations. The default is
+    always.
    
+
+
    
+
    top
    
+
    AuthLDAPGroupAttribute Directive
    
+
+
+
+
+
+
+
+
+
    Description:LDAP attributes used to identify the user members of
+groups.
    Syntax:AuthLDAPGroupAttribute attribute
    Default:AuthLDAPGroupAttribute member uniquemember
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
+    
    This directive specifies which LDAP attributes are used to
+    check for user members within groups. Multiple attributes can be used
+    by specifying this directive multiple times. If not specified,
+    then mod_authnz_ldap uses the member and
+    uniquemember attributes.
    
+
+
    
+
    top
    
+
    AuthLDAPGroupAttributeIsDN Directive
    
+
+
+
+
+
+
+
+
+
    Description:Use the DN of the client username when checking for
+group membership
    Syntax:AuthLDAPGroupAttributeIsDN on|off
    Default:AuthLDAPGroupAttributeIsDN on
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
+    
    When set on, this directive says to use the
+    distinguished name of the client username when checking for group
+    membership.  Otherwise, the username will be used. For example,
+    assume that the client sent the username bjenson,
+    which corresponds to the LDAP DN cn=Babs Jenson,
+    o=Example. If this directive is set,
+    mod_authnz_ldap will check if the group has
+    cn=Babs Jenson, o=Example as a member. If this
+    directive is not set, then mod_authnz_ldap will
+    check if the group has bjenson as a member.
    
+
+
    
+
    top
    
+
    AuthLDAPInitialBindAsUser Directive
    
+
+
+
+
+
+
+
+
+
+
    Description:Determines if the server does the initial DN lookup using the basic authentication users'
+own username, instead of anonymously or with hard-coded credentials for the server
    Syntax:AuthLDAPInitialBindAsUser off|on
    Default:AuthLDAPInitialBindAsUser off
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.6 and later
    
+    
    By default, the server either anonymously, or with a dedicated user and
+     password, converts the basic authentication username into an LDAP
+     distinguished name (DN).  This directive forces the server to use the verbatim username
+     and password provided by the incoming user to perform the initial DN
+     search.
    
+
+     
     If the verbatim username can't directly bind, but needs some
+     cosmetic transformation, see 
+     AuthLDAPInitialBindPattern.
    
+
+     
     This directive should only be used when your LDAP server doesn't
+         accept anonymous searches and you cannot use a dedicated
+         AuthLDAPBindDN.
+     
    
+
+     
    Not available with authorization-only
    
+         This directive can only be used if this module authenticates the user, and
+         has no effect when this module is used exclusively for authorization.
+     
    
+
+
    See also
    
+
+
    
+
    top
    
+
    AuthLDAPInitialBindPattern Directive
    
+
+
+
+
+
+
+
+
+
+
    Description:Specifies the transformation of the basic authentication username to be used when binding to the LDAP server
+to perform a DN lookup
    Syntax:AuthLDAPInitialBindPatternregex substitution
    Default:AuthLDAPInitialBindPattern (.*) $1 (remote username used verbatim)
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.6 and later
    
+    
    If AuthLDAPInitialBindAsUser is set to
+       ON, the basic authentication username will be transformed according to the
+       regular expression and substituion arguments.
    
+
+    
     The regular expression argument is compared against the current basic authentication username.
+        The substitution argument may contain backreferences, but has no other variable interpolation.
    
+
+    
     This directive should only be used when your LDAP server doesn't
+        accept anonymous searches and you cannot use a dedicated
+        AuthLDAPBindDN.
+    
    
+
+    
    AuthLDAPInitialBindPattern (.+) $1@example.com
    
+
+    
    AuthLDAPInitialBindPattern (.+) cn=$1,dc=example,dc=com
    
+
+
+    
    Not available with authorization-only
    
+        This directive can only be used if this module authenticates the user, and
+        has no effect when this module is used exclusively for authorization.
+    
    
+    
    debugging
    
+        The substituted DN is recorded in the environment variable
+        LDAP_BINDASUSER.  If the regular expression does not match the input,
+        the verbatim username is used.
+    
    
+
+
    See also
    
+
+
    
+
    top
    
+
    AuthLDAPMaxSubGroupDepth Directive
    
+
+
+
+
+
+
+
+
+
+
    Description:Specifies the maximum sub-group nesting depth that will be
+evaluated before the user search is discontinued.
    Syntax:AuthLDAPMaxSubGroupDepth Number
    Default:AuthLDAPMaxSubGroupDepth 0
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.0 and later, defaulted to 10 in 2.4.x and early 2.5
    
+   
    When this directive is set to a non-zero value X
+   combined with use of the Require ldap-group someGroupDN
+   directive, the provided user credentials will be searched for
+   as a member of the someGroupDN directory object or of
+   any group member of the current group up to the maximum nesting
+   level X specified by this directive.
    
+   
    See the Require ldap-group
+   section for a more detailed example.
    
+
+   
    Nested groups performance
    
+   
     When AuthLDAPSubGroupAttribute overlaps with
+   AuthLDAPGroupAttribute (as it does by default and
+   as required by common LDAP schemas), uncached searching for subgroups in 
+   large groups can be very slow. If you use large, non-nested groups, keep 
+   AuthLDAPMaxSubGroupDepth set to zero.
    
+   
    
+
+
+
    
+
    top
    
+
    AuthLDAPRemoteUserAttribute Directive
    
+
+
+
+
+
+
+
+
+
    Description:Use the value of the attribute returned during the user
+query to set the REMOTE_USER environment variable
    Syntax:AuthLDAPRemoteUserAttribute uid
    Default:none
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
+    
    If this directive is set, the value of the
+    REMOTE_USER environment variable will be set to the
+    value of the attribute specified. Make sure that this attribute is
+    included in the list of attributes in the AuthLDAPUrl definition,
+    otherwise this directive will have no effect. This directive, if
+    present, takes precedence over AuthLDAPRemoteUserIsDN. This
+    directive is useful should you want people to log into a website
+    using an email address, but a backend application expects the
+    username as a userid.
    
+    
     This directive only has effect when this module is used for 
+    authentication.
    
+
+
    
+
    top
    
+
    AuthLDAPRemoteUserIsDN Directive
    
+
+
+
+
+
+
+
+
+
    Description:Use the DN of the client username to set the REMOTE_USER
+environment variable
    Syntax:AuthLDAPRemoteUserIsDN on|off
    Default:AuthLDAPRemoteUserIsDN off
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
+    
    If this directive is set to on, the value of the
+    REMOTE_USER environment variable will be set to the full
+    distinguished name of the authenticated user, rather than just
+    the username that was passed by the client. It is turned off by
+    default.
    
+    
     This directive only has effect when this module is used for
+    authentication.
    
+
+
    
+
    top
    
+
    AuthLDAPSearchAsUser Directive
    
+
+
+
+
+
+
+
+
+
+
    Description:Use the authenticated user's credentials to perform authorization searches
    Syntax:AuthLDAPSearchAsUser on|off
    Default:AuthLDAPSearchAsUser off
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.6 and later
    
+    
    When set, and mod_authnz_ldap has authenticated the
+    user, LDAP searches for authorization use the queried distinguished name (DN)
+    and HTTP basic authentication password of the authenticated user instead of
+    the servers configured credentials.
    
+
+    
     The ldap-filter and ldap-dn authorization
+    checks use searches.
    
+
+    
    This directive only has effect on the comparisons performed during
+    nested group processing when 
+    AuthLDAPCompareAsUser is also enabled.
    
+
+    
     This directive should only be used when your LDAP server doesn't
+        accept anonymous searches and you cannot use a dedicated
+        AuthLDAPBindDN.
+    
    
+
+
    See also
    
+
+
    
+
    top
    
+
    AuthLDAPSubGroupAttribute Directive
    
+
+
+
+
+
+
+
+
+
+
    Description:Specifies the attribute labels, one value per
+directive line, used to distinguish the members of the current group that
+are groups.
    Syntax:AuthLDAPSubGroupAttribute attribute
    Default:AuthLDAPSubgroupAttribute member uniquemember
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.0 and later
    
+    
    An LDAP group object may contain members that are users and
+    members that are groups (called nested or sub groups). The
+    AuthLDAPSubGroupAttribute directive identifies the
+    labels of group members and the AuthLDAPGroupAttribute
+    directive identifies the labels of the user members. Multiple
+    attributes can be used by specifying this directive multiple times.
+    If not specified, then mod_authnz_ldap uses the
+    member and uniqueMember attributes.
    
+
+
    
+
    top
    
+
    AuthLDAPSubGroupClass Directive
    
+
+
+
+
+
+
+
+
+
+
    Description:Specifies which LDAP objectClass values identify directory
+objects that are groups during sub-group processing.
    Syntax:AuthLDAPSubGroupClass LdapObjectClass
    Default:AuthLDAPSubGroupClass groupOfNames groupOfUniqueNames
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    Compatibility:Available in version 2.3.0 and later
    
+    
    An LDAP group object may contain members that are users and
+    members that are groups (called nested or sub groups). The
+    AuthLDAPSubGroupAttribute directive identifies the
+    labels of members that may be sub-groups of the current group
+    (as opposed to user members). The AuthLDAPSubGroupClass
+    directive specifies the LDAP objectClass values used in verifying that
+    these potential sub-groups are in fact group objects. Verified sub-groups
+    can then be searched for more user or sub-group members. Multiple
+    attributes can be used by specifying this directive multiple times.
+    If not specified, then mod_authnz_ldap uses the
+    groupOfNames and groupOfUniqueNames values.
    
+
+
    
+
    top
    
+
    AuthLDAPUrl Directive
    
+
+
+
+
+
+
+
+
    Description:URL specifying the LDAP search parameters
    Syntax:AuthLDAPUrl url [NONE|SSL|TLS|STARTTLS]
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Extension
    Module:mod_authnz_ldap
    
+    
    An RFC 2255 URL which specifies the LDAP search parameters
+    to use. The syntax of the URL is
    
+
    ldap://host:port/basedn?attribute?scope?filter
    
+    
    If you want to specify more than one LDAP URL that Apache should try in turn, the syntax is:
    
+
    AuthLDAPUrl "ldap://ldap1.example.com ldap2.example.com/dc=..."
    
+
+
    Caveat: If you specify multiple servers, you need to enclose the entire URL string in quotes;
+otherwise you will get an error: "AuthLDAPURL takes one argument, URL to define LDAP connection.." 
+You can of course use search parameters on each of these.
    
+
+
    
+
    ldap
    
+
+        
    For regular ldap, use the
+        string ldap. For secure LDAP, use ldaps
+        instead. Secure LDAP is only available if Apache was linked
+        to an LDAP library with SSL support.
    
+
+
    host:port
    
+
+        
    
+          
    The name/port of the ldap server (defaults to
+          localhost:389 for ldap, and
+          localhost:636 for ldaps). To
+          specify multiple, redundant LDAP servers, just list all
+          servers, separated by spaces. mod_authnz_ldap
+          will try connecting to each server in turn, until it makes a
+          successful connection. If multiple ldap servers are specified,
+          then entire LDAP URL must be encapsulated in double quotes.
    
+
+          
    Once a connection has been made to a server, that
+          connection remains active for the life of the
+          httpd process, or until the LDAP server goes
+          down.
    
+
+          
    If the LDAP server goes down and breaks an existing
+          connection, mod_authnz_ldap will attempt to
+          re-connect, starting with the primary server, and trying
+          each redundant server in turn. Note that this is different
+          than a true round-robin search.
    
+        
    
+
+
    basedn
    
+
+        
    The DN of the branch of the
+        directory where all searches should start from. At the very
+        least, this must be the top of your directory tree, but
+        could also specify a subtree in the directory.
    
+
+
    attribute
    
+
+        
    The attribute to search for.
+        Although RFC 2255 allows a comma-separated list of
+        attributes, only the first attribute will be used, no
+        matter how many are provided. If no attributes are
+        provided, the default is to use uid. It's a good
+        idea to choose an attribute that will be unique across all
+        entries in the subtree you will be using.  All attributes
+        listed will be put into the environment with an AUTHENTICATE_ prefix
+        for use by other modules.
    
+
+
    scope
    
+
+        
    The scope of the search. Can be either one or
+        sub. Note that a scope of base is
+        also supported by RFC 2255, but is not supported by this
+        module. If the scope is not provided, or if base scope
+        is specified, the default is to use a scope of
+        sub.
    
+
+
    filter
    
+
+        
    A valid LDAP search filter. If
+        not provided, defaults to (objectClass=*), which
+        will search for all objects in the tree. Filters are
+        limited to approximately 8000 characters (the definition of
+        MAX_STRING_LEN in the Apache source code). This
+        should be more than sufficient for any application. The keyword
+        none disables the use of a filter; this is required
+        by some primitive LDAP servers.
    
+
    
+
+    
    When doing searches, the attribute, filter and username passed
+    by the HTTP client are combined to create a search filter that
+    looks like
+    (&(filter)(attribute=username)).
    
+
+    
    For example, consider an URL of
+    ldap://ldap.example.com/o=Example?cn?sub?(posixid=*). When
+    a client attempts to connect using a username of Babs
+    Jenson, the resulting search filter will be
+    (&(posixid=*)(cn=Babs Jenson)).
    
+
+    
    An optional parameter can be added to allow the LDAP Url to override
+    the connection type.  This parameter can be one of the following:
    
+
+
    
+    
    NONE
    
+        
    Establish an unsecure connection on the default LDAP port. This
+        is the same as ldap:// on port 389.
    
+    
    SSL
    
+        
    Establish a secure connection on the default secure LDAP port.
+        This is the same as ldaps://
    
+    
    TLS | STARTTLS
    
+        
    Establish an upgraded secure connection on the default LDAP port.
+        This connection will be initiated on port 389 by default and then
+        upgraded to a secure connection on the same port.
    
+
    
+
+    
    See above for examples of AuthLDAPURL URLs.
    
+
 
    
 
    
 
    
diff --git a/docs/manual/mod/mod_authnz_ldap.html.fr b/docs/manual/mod/mod_authnz_ldap.html.fr
index a3f86653b5..c2ee3e0263 100644
--- a/docs/manual/mod/mod_authnz_ldap.html.fr
+++ b/docs/manual/mod/mod_authnz_ldap.html.fr
@@ -63,7 +63,21 @@ HTTP de base.
    
 
    
-
-
-
-
-
-
-
-
-
    Description:Spcifie le prfixe ajout aux variables d'environnement
-durant la phase d'autorisation
    Syntaxe:AuthLDAPAuthorizePrefix prfixe
    Dfaut:AuthLDAPAuthorizePrefix AUTHORIZE_
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible depuis la version 2.3.6
    
-    
    Cette directive permet de spcifier le prfixe ajout aux
-    variables d'environnement durant la phase d'autorisation. Si la
-    valeur spcifie est AUTHENTICATE_, les utilisateurs de ces
-    variables d'environnement verront les mmes informations, que le
-    serveur effectue une authentification, une autorisation, ou les
-    deux.
    
-
-    
    Note
    
-    Aucune variable d'autorisation n'est dfinie lorsqu'un utilisateur
-    s'est vu autoriser l'accs via la directive Require
-    valid-user.
-    
    
-
-
    
-
    top
    
-
    Directive AuthLDAPBindAuthoritative
    
-
-
-
-
-
-
-
-
-
    Description:Dtermine si l'on doit utiliser d'autres fournisseurs
-d'authentification lorsque le serveur ne peut pas valider les donnes
-d'authentification de l'utilisateur, alors que ce dernier possde un
-DN.
    Syntaxe:AuthLDAPBindAuthoritativeoff|on
    Dfaut:AuthLDAPBindAuthoritative on
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
-    
    Par dfaut, des fournisseurs d'authentification sont appels
-    si un utilisateur ne possde pas de DN, mais ne le sont pas si
-    l'utilisateur possde un DN et si son mot de passe ne peut pas tre
-    vrifi lors d'une connexion au serveur LDAP. Si la directive
-    AuthLDAPBindAuthoritative est
-    dfinie  off, d'autres modules d'authentification
-    configurs auront une chance de valider le mot de passe de
-    l'utilisateur si la tentative de connexion au serveur LDAP choue
-    pour une raison quelconque (avec les donnes d'authentification
-    fournies).
    
-    
    Ceci permet aux utilisateurs prsent  la fois dans l'annuaire
-    LDAP et dans un fichier AuthUserFile de s'authentifier
-    lorsque le serveur LDAP est disponible, alors que le compte de
-    l'utilisateur est verrouill ou que son mot de passe est
-    inutilisable pour une raison quelconque.
    
-
-
    Voir aussi
    
-
-
    
-
    top
    
-
    Directive AuthLDAPBindDN
    
-
-
-
-
-
-
-
-
    Description:Un DN optionnel pour se connecter au serveur
-LDAP
    Syntaxe:AuthLDAPBindDN dn
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
-    
    Cette directive permet de dfinir un DN optionnel pour se
-    connecter au serveur afin d'y rechercher des entres. Si aucun DN
-    n'est spcifi, mod_authnz_ldap tentera une
-    connexion anonyme.
    
-
-
    
-
    top
    
-
    Directive AuthLDAPBindPassword
    
-
-
-
-
-
-
-
-
-
    Description:Mot de passe  utiliser en conjonction avec le DN de
-connexion
    Syntaxe:AuthLDAPBindPassword mot-de-passe
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:exec: est disponible depuis la version 2.4.5 du
-serveur HTTP Apache.
    
-    
    Cette directive permet de spcifier un mot de passe  utiliser en
-    conjonction avec le DN de connexion. Notez que ce mot de passe
-    constitue en gnral une donne sensible, et doit donc tre protg
-    de manire approprie. Vous ne devez utiliser les directives
-    AuthLDAPBindDN et AuthLDAPBindPassword que si
-    vous en avez vraiment besoin pour effectuer une recherche dans
-    l'annuaire.
    
-
-    
    Si la valeur commence par exec:, la commande rsultante sera
-    excute, et la premire ligne renvoye sur la sortie standard sera
-    utilise comme mot de passe.
    
-
    #Mot de passe utilis tel quel
-AuthLDAPBindPassword secret
-
-#Excute /path/to/program pour obtenir le mot de passe
-AuthLDAPBindPassword exec:/path/to/program
-
-#Excute /path/to/otherProgram avec un argument pour obtenir le mot de passe
-AuthLDAPBindPassword "exec:/path/to/otherProgram argument1"
    
-
-
-
-
    
-
    top
    
-
    Directive AuthLDAPCharsetConfig
    
-
-
-
-
-
-
-
    Description:Chemin du fichier de configuration de la correspondance
-langage/jeu de caractres
    Syntaxe:AuthLDAPCharsetConfig chemin-fichier
    Contexte:configuration du serveur
    Statut:Extension
    Module:mod_authnz_ldap
    
-    
    La directive AuthLDAPCharsetConfig permet
-    de dfinir le chemin du fichier de configuration de la
-    correspondance langage/jeu de caractres. chemin-fichier
-    est un chemin relatif au rpertoire dfini par la directive
-    ServerRoot. Ce fichier contient une liste
-    de correspondances extension de langage/jeu de caractres. La
-    plupart des administrateurs utilisent le fichier
-    charset.conv fourni qui associe les extensions de
-    langage courantes  leurs jeux de caractres.
    
-
-    
    Le fichier contient des lignes au format suivant :
    
-
-    
    
-      extension de langage jeu de caractres
-      [Nom du langage] ...
-    
    
-
-    
    L'extension est insensible  la casse. Les lignes vides et les
-    lignes commenant par un dise (#) sont ignores.
    
-
-
    
-
    top
    
-
    Directive AuthLDAPCompareAsUser
    
-
-
-
-
-
-
-
-
-
-
    Description:Utilisation des donnes d'authentification de l'utilisateur
-pour effectuer les comparaisons pour l'attribution des autorisations
    Syntaxe:AuthLDAPCompareAsUser on|off
    Dfaut:AuthLDAPCompareAsUser off
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible depuis la version version 2.3.6
    
-    
    Lorsque cette directive est dfinie, et si
-    mod_authnz_ldap a authentifi l'utilisateur, les
-    recherches LDAP pour les autorisations utilisent le nom distinctif
-    trouv (DN) et le mot de passe d'authentification basique HTTP de
-    l'utilisateur authentifi au lieu des donnes d'authentification
-    configures au niveau du serveur.
    
-
-    
    Les vrifications d'autorisation ldap-attribute,
-    ldap-user, et ldap-group (niveau simple seulement)
-    utilisent des comparaisons.
    
-
-    
    Cette directive n'a d'effet sur les comparaisons effectues au
-    cours des traitements de groupe imbriqus, et lorsque la directive
-    AuthLDAPSearchAsUser
-    est aussi active.
    
-
-    
    Cette directive ne doit tre utilise que si votre serveur LDAP
-     n'autorise pas les recherches anonymes, ou si vous ne pouvez pas
-     utiliser de nom d'utilisateur ddi via la directive AuthLDAPBindDN.
-     
    
-
-
    Voir aussi
    
-
-
    
-
    top
    
-
    Directive AuthLDAPCompareDNOnServer
    
-
-
-
-
-
-
-
-
-
    Description:Utilise le serveur LDAP pour comparer les DNs
    Syntaxe:AuthLDAPCompareDNOnServer on|off
    Dfaut:AuthLDAPCompareDNOnServer on
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
-    
    Lorsque cette directive est dfinie  on,
-    mod_authnz_ldap utilise le serveur LDAP pour
-    comparer les DNs. Il s'agit de la seule mthode infaillible pour
-    comparer les DNs. mod_authnz_ldap va rechercher
-    dans l'annuaire le DN spcifi par la directive Require dn, puis extraire ce DN et le
-    comparer avec le DN extrait de l'entre de l'utilisateur. Si cette
-    directive est  off, mod_authnz_ldap effectue une
-    simple comparaison de chanes. Cette dernire approche peut produire
-    des faux ngatifs, mais elle est beaucoup plus rapide. Notez
-    cependant que le cache de mod_ldap peut acclrer
-    la comparaison de DNs dans la plupart des situations.
    
-
-
    
-
    top
    
-
    Directive AuthLDAPDereferenceAliases
    
-
-
-
-
-
-
-
-
-
    Description: quel moment le module va drfrencer les
-alias
    Syntaxe:AuthLDAPDereferenceAliases never|searching|finding|always
    Dfaut:AuthLDAPDereferenceAliases always
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
-    
    Cette directive permet de spcifier  quel moment
-    mod_authnz_ldap va drfrencer les alias au cours
-    des oprations lies  LDAP. La valeur par dfaut est
-    always.
    
-
-
    
-
    top
    
-
    Directive AuthLDAPGroupAttribute
    
-
-
-
-
-
-
-
-
-
    Description:L'attribut LDAP utilis pour vrifier l'appartenance d'un
-utilisateur  un groupe.
    Syntaxe:AuthLDAPGroupAttribute attribut
    Dfaut:AuthLDAPGroupAttribute member uniquemember
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
-    
    Cette directive permet de spcifier quel attribut LDAP est
-    utilis pour vrifier l'appartenance d'un utilisateur  un
-    groupe. On peut spcifier plusieurs attributs en rptant cette
-    directive plusieurs fois. Si la directive n'est pas dfinie,
-    mod_authnz_ldap utilise les attributs
-    member et uniquemember.
    
-
-
    
-
    top
    
-
    Directive AuthLDAPGroupAttributeIsDN
    
-
-
-
-
-
-
-
-
-
    Description:Utilise le DN de l'utilisateur pour vrifier son
-appartenance  un groupe
    Syntaxe:AuthLDAPGroupAttributeIsDN on|off
    Dfaut:AuthLDAPGroupAttributeIsDN on
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
-    
    Lorsqu'elle est dfinie  on, cette directive
-    indique que c'est le DN de l'utilisateur qui doit tre utilis pour
-    vrifier son appartenance  un groupe. Dans le cas contraire, c'est
-    le nom de l'utilisateur qui sera utilis. Par exemple, supposons que
-    le client envoie le nom d'utilisateur bjenson, qui
-    correspond au DN LDAP cn=Babs Jenson,o=Example. Si la
-    directive est  on, mod_authnz_ldap va
-    vrifier si cn=Babs Jenson, o=Example est un membre du
-    groupe. Dans le cas contraire, mod_authnz_ldap
-    vrifiera si bjenson est un membre du groupe.
    
-
-
    
-
    top
    
-
    Directive AuthLDAPInitialBindAsUser
    
-
-
-
-
-
-
-
-
-
-
    Description:Dtermine si le serveur effectue la recherche initiale du
-DN en utilisant le nom propre de l'utilisateur pour l'authentification
-de base
-et non de manire anonyme, ou en utilisant des donnes d'authentification
-codes en dur pour le serveur
    Syntaxe:AuthLDAPInitialBindAsUser off|on
    Dfaut:AuthLDAPInitialBindAsUser off
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible depuis la version 2.3.6
    
-    
    Par dfaut, le serveur convertit le nom d'utilisateur pour
-    l'authentification de base en nom distinctif LDAP (DN) soit de
-    manire anonyme, soit avec un couple nom/mot de passe ddi. Cette
-    directive permet de forcer le serveur  utiliser les vritables nom
-    d'utilisateur et mot de passe fournis par l'utilisateur pour
-    effectuer la recherche initiale du DN.
    
-
-     
    Si le nom d'utilisateur ne peut pas s'authentifier directement
-     et ncessite de lgres modifications, voir la directive AuthLDAPInitialBindPattern.
    
-
-     
    Cette directive ne doit tre utilise que si votre serveur LDAP
-     n'autorise pas les recherches anonymes, ou si vous ne pouvez pas
-     utiliser de nom d'utilisateur ddi via la directive AuthLDAPBindDN.
-     
    
-
-     
    Non disponible dans la cas d'une autorisation seule
    
-         On ne peut utiliser cette directive que si ce module
-	 effectue une authentification, et n'a aucun effet si ce module
-	 n'est utilis que pour les processus d'autorisation.
-     
    
-
-
    Voir aussi
    
-
-
    
-
    top
    
-
    Directive AuthLDAPInitialBindPattern
    
-
-
-
-
-
-
-
-
-
-
    Description:Spcifie la modification a apporter au nom d'utilisateur
-pour l'authentification de base lors de l'authentification auprs du
-serveur LDAP pour effectuer une recherche de DN
    Syntaxe:AuthLDAPInitialBindPatternregex substitution
    Dfaut:AuthLDAPInitialBindPattern (.*) $1 (nom de l'utilisateur
-distant utilis tel quel)
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible depuis la version 2.3.6
    
-    
    Si la directive AuthLDAPInitialBindAsUser est
-    dfinie  ON, le nom utilisateur pour l'authentification de
-    base sera transform selon l'expression rationnelle
-    regex et l'argument substitution spcifis.
    
-
-    
    L'expression rationnelle est compare au nom d'utilisateur pour
-    l'authentification de base courant. L'argument
-    substitution peut contenir des rfrences arrires, mais
-    n'effectue aucune autre interpolation de variable.
    
-
-    
    Cette directive ne doit tre utilise que si votre serveur LDAP
-     n'autorise pas les recherches anonymes, ou si vous ne pouvez pas
-     utiliser de nom d'utilisateur ddi via la directive AuthLDAPBindDN.
-     
    
-
-    
    AuthLDAPInitialBindPattern (.+) $1@example.com
    
-
-    
    AuthLDAPInitialBindPattern (.+) cn=$1,dc=example,dc=com
    
-
-
-    
    Non disponible dans la cas d'une autorisation seule
    
-         On ne peut utiliser cette directive que si ce module
-	 effectue une authentification, et n'a aucun effet si ce module
-	 n'est utilis que pour les processus d'autorisation.
-     
    
-    
    Dbogage
    
-        Le DN de substitution est enregistr dans la variable
-	d'environnement LDAP_BINDASUSER. Si l'expression
-	rationnelle ne convient pas, le nom d'utilisateur est utilis
-	tel quel.
-    
    
-
-
    Voir aussi
    
-
-
    
-
    top
    
-
    Directive AuthLDAPMaxSubGroupDepth
    
-
-
-
-
-
-
-
-
-
-
    Description:Spcifie la profondeur d'imbrication des sous-groupes
-maximale prise en compte avant l'abandon de la recherche de
-l'utilisateur.
    Syntaxe:AuthLDAPMaxSubGroupDepth Nombre
    Dfaut:AuthLDAPMaxSubGroupDepth 0
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible  partir de la version 2.3.0 du serveur HTTP
-Apache ; la valeur par dfaut tait 10 dans les versions 2.4.x et les
-premires versions 2.5
    
-   
    Lorsque cette directive est dfinie  une valeur X
-   non nulle, en combinaison avec l'utilisation de la directive
-   Require ldap-group DN-groupe, les donnes de connexion
-   fournies seront utilises pour vrifier l'appartenance de
-   l'utilisateur  l'objet de l'annuaire DN-groupe ou 
-   tout sous-groupe du groupe courant en tenant compte de la profondeur
-   d'imbrication maximale X spcifie par la directive.
    
-   
    Se rfrer  la section Require
-   ldap-group pour un exemple plus dtaill.
    
-
-   
    Performances dans le cas des groupes imbriqus
    
-   
    Lorsque les directives
-   AuthLDAPSubGroupAttribute et
-   AuthLDAPGroupAttribute se recouvrent (comme
-   c'est le cas par dfaut et requis par les schmas LDAP courants), la
-   recherche de sous-groupes au sein de grands groupes peut tre trs
-   longue. Si vos groupes sont trs grands et non imbriqus, dfinissez
-   la directive AuthLDAPMaxSubGroupDepth  0.
    
-   
    
-
-
-
    
-
    top
    
-
    Directive AuthLDAPRemoteUserAttribute
    
-
-
-
-
-
-
-
-
-
    Description:Spcifie l'attribut dont la valeur renvoye au cours de la
-requte de l'utilisateur sera utilise pour dfinir la variable
-d'environnement REMOTE_USER
    Syntaxe:AuthLDAPRemoteUserAttribute uid
    Dfaut:none
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
-    
    Lorsque cette directive est dfinie, la variable d'environnement
-    REMOTE_USER sera dfinie  la valeur de l'attribut
-    spcifi. Assurez-vous que cet attribut soit bien inclus dans la
-    liste d'attributs spcifis dans la dfinition de AuthLDAPUrl ; dans
-    le cas contraire, cette directive n'aurait aucun effet. Si elle est
-    prsente, cette directive l'emporte sur AuthLDAPRemoteUserIsDN. Elle
-    peut s'avrer utile par exemple, si vous souhaitez que les
-    utilisateurs se connectent  un site web en utilisant leur adresse
-    email, alors qu'une application sous-jacente ncessite un nom
-    d'utilisateur comme identifiant.
    
-    
    Cette directive n'a d'effet que si l'on utilise ce module pour
-    l'authentification.
    
-
-
    
-
    top
    
-
    Directive AuthLDAPRemoteUserIsDN
    
-
-
-
-
-
-
-
-
-
    Description:Utilise le DN de l'utilisateur pour dfinir la variable
-d'environnement REMOTE_USER
    Syntaxe:AuthLDAPRemoteUserIsDN on|off
    Dfaut:AuthLDAPRemoteUserIsDN off
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
-    
    Lorsque cette directive est  on, la variable d'environnement
-    REMOTE_USER sera dfinie avec la valeur du DN complet
-    de l'utilisateur authentifi, et non plus avec simplement le nom
-    d'utilisateur fourni par le client. Elle est dfinie  off par
-    dfaut.
    
-    
    Cette directive n'a d'effet que si l'on utilise ce module pour
-    l'authentification.
    
-
-
    
-
    top
    
-
    Directive AuthLDAPSearchAsUser
    
-
-
-
-
-
-
-
-
-
-
    Description:Utilise les donnes d'authentification de l'utilisateur
-pour la recherche des autorisations
    Syntaxe:AuthLDAPSearchAsUser on|off
    Dfaut:AuthLDAPSearchAsUser off
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible depuis la version 2.3.6
    
-    
    Lorsque cette directive est dfinie, et si
-    mod_authnz_ldap a authentifi l'utilisateur, les
-    recherches LDAP pour dfinir les autorisations utilisent le nom
-    distinctif (DN) trouv et le mot de passe pour l'authentification de
-    base HTTP de l'utilisateur authentifi, au lieu des donnes
-    d'authentification configures au niveau du serveur.
    
-
-    
    Les vrifications d'autorisation ldap-filter et
-    ldap-dn utilisent des recherches.
    
-
-    
    Cette directive n'a d'effet sur les comparaisons effectues au
-    cours des traitements de groupe imbriqus, et lorsque la directive
-    AuthLDAPCompareAsUser
-    est aussi active.
    
-
-     
    Cette directive ne doit tre utilise que si votre serveur LDAP
-     n'autorise pas les recherches anonymes, ou si vous ne pouvez pas
-     utiliser de nom d'utilisateur ddi via la directive AuthLDAPBindDN.
-     
    
-
-
-
    Voir aussi
    
-
-
    
-
    top
    
-
    Directive AuthLDAPSubGroupAttribute
    
-
-
-
-
-
-
-
-
-
-
    Description:Spcifie les noms d'attribut, un par directive, utiliss
-pour diffrencier les membres du groupe courant qui sont eux-mmes des
-groupes.
    Syntaxe:AuthLDAPSubGroupAttribute attribut
    Dfaut:AuthLDAPSubgroupAttribute member uniquemember
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible  partir de la version 2.3.0 du serveur HTTP
-Apache
    
-    
    Un objet groupe LDAP peut contenir des membres qui sont des
-    utilisateurs et des membres qui sont eux-mmes des groupes (appels
-    sous-groupes ou groupes imbriqus). La directive
-    AuthLDAPSubGroupAttribute spcifie l'attribut utilis
-    pour identifier les groupes, alors que la directive
-    AuthLDAPGroupAttribute spcifie l'attribut utilis
-    pour identifier les utilisateurs. On peut spcifier plusieurs
-    attributs en rptant la directive plusieurs fois. Si elle n'est pas
-    dfinie, mod_authnz_ldap utilise les attributs
-    member et uniqueMember.
    
-
-
    
-
    top
    
-
    Directive AuthLDAPSubGroupClass
    
-
-
-
-
-
-
-
-
-
-
    Description:Spcifie quelles valeurs d'objectClass LDAP identifient les
-objets de l'annuaire qui sont des groupes au cours du traitement des
-sous-groupes.
    Syntaxe:AuthLDAPSubGroupClass ObjectClass-LDAP
    Dfaut:AuthLDAPSubGroupClass groupOfNames groupOfUniqueNames
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible  partir de la version 2.3.0 du serveur HTTP
-Apache
    
-    
    Un objet groupe LDAP peut contenir des membres qui sont des
-    utilisateurs et des membres qui sont eux-mmes des groupes (appels
-    sous-groupes ou groupes imbriqus). La directive
-    AuthLDAPSubGroupAttribute permet d'identifier les
-    membres qui sont des sous-groupes du groupe courant ( l'oppos des
-    membres utilisateurs). La directive
-    AuthLDAPSubGroupClass permet de spcifier les valeurs
-    d'objectClass LDAP utilises pour vrifier que certains membres sont
-    en fait des objets groupe. Les sous-groupes ainsi identifis peuvent
-    alors faire l'objet d'une recherche d'autres membres utilisateurs ou
-    sous-groupes. On peut spcifier plusieurs attributs en rptant
-    cette directive plusieurs fois. Si cette directive n'est pas
-    dfinie, mod_authnz_ldap utilise les attributs
-    groupOfNames et groupOfUniqueNames.
    
-
-
    
-
    top
    
-
    Directive AuthLDAPUrl
    
-
-
-
-
-
-
-
-
    Description:L'URL permettant de spcifier les paramtres de la
-recherche LDAP
    Syntaxe:AuthLDAPUrl url [NONE|SSL|TLS|STARTTLS]
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
-    
    Une URL conforme  la RFC 2255 qui permet de spcifier les
-    paramtres  utiliser pour la recherche dans l'annuaire LDAP. La
-    syntaxe de l'URL est :
    
-
    ldap://hte:port/DN-de-base?attribut?porte?filtre
    
-    
    Si vous souhaitez mettre  la disposition d'Apache plusieurs URLs
-    LDAP, la syntaxe sera :
    
-
    AuthLDAPUrl "ldap://ldap1.example.com ldap2.example.com/dc=..."
    
-
-
    Mise en garde : Si vous spcifiez plusieurs
-serveurs, vous devez en entourer la liste avec des guillemets ; dans le
-cas contraire, vous gnrerez une erreur : "AuthLDAPURL takes one
-argument, URL to define LDAP connection..". Vous pouvez bien
-entendu ajouter des paramtres de recherche  chacun des serveurs
-spcifis.
    
-
-
    
-
    ldap
    
-
-        
    Pour ldap non scuris, utilisez la chane
-	ldap. Pour ldap scuris, utilisez  la place la
-	chane ldaps. LDAP scuris n'est disponible que si
-	Apache a t li avec une bibliothque LDAP supportant SSL.
    
-
-
    hte:port
    
-
-        
    
-          
    Il s'agit du nom/port du serveur ldap
-	  (dont la valeur par dfaut est
-	  localhost:389 pour ldap, et
-	  localhost:636 pour ldaps). Pour
-	  spcifier plusieurs serveurs LDAP redondants, indiquez
-	  simplement leur liste en les sparant par des espaces.
-	  mod_authnz_ldap tentera alors de se connecter
-	   chacun des serveurs jusqu' ce qu'il parvienne  se
-	  connecter avec succs. Notez qu'en cas de multiples serveurs
-	  LDAP, l'ensemble de l'URL LDAP doit tre entoure de
-	  guillemets.
    
-
-          
    lorsqu'une connection a t tablie avec un serveur, elle
-	  reste active pendant toute la dure de vie du processus
-	  httpd, ou jusqu' ce que le serveur LDAP
-	  cesse de fonctionner.
    
-
-          
    Si le serveur LDAP cesse de fonctionner, et ainsi
-	  interrompt une
-	  connexion existante, mod_authnz_ldap tentera
-	  de se reconnecter en commenant par le premier serveur de la
-	  liste, et ainsi de suite avec les serveurs redondants
-	  suivants. Notez que ce processus n'a rien  voir avec une
-	  vritable recherche de type round-robin.
    
-        
    
-
-
    DN-de-base
    
-        
    Le DN de la branche de l'annuaire  partir de laquelle
-	toutes les recherches seront lances. Il doit au moins
-	correspondre  la racine de votre annuaire, mais vous pouvez
-	aussi indiquer une branche plus spcifique.
    
-
-
    attribut
    
-
-        
    Il s'agit de l'attribut  utiliser pour la recherche.
-	Bien que la RFC
-	2255 autorise une liste d'attributs spars par des virgules,
-	seul le premier sera retenu, sans tenir compte des autres
-	attributs fournis. Si aucun attribut n'est fourni, l'attribut
-	par dfaut est uid. Il est judicieux de choisir un
-	attribut dont la valeur sera unique parmi toutes les entres de
-	la branche de l'annuaire que vous aurez dfinie. Tous les
-	attributs spcifis seront enregistrs dans des variables
-	d'environnement avec le prfixe AUTHENTICATE_, afin de pouvoir
-	tre utiliss par d'autres modules.
    
-
-
    porte
    
-
-        
    Il s'agit de la porte de la recherche. Elle peut prendre
-	les valeurs one ou sub. Notez que la
-	RFC 2255 supporte aussi une porte de valeur base,
-	mais cette dernire n'est pas supporte par le module. Si la
-	porte n'est pas dfinie, ou si elle est dfinie 
-	base, c'est la valeur de porte par dfaut
-	sub qui sera utilise.
    
-
-
    filtre
    
-
-        
    Il s'agit d'un filtre de recherche LDAP valide. Si aucun
-	filtre n'est spcifi, le filtre par dfaut
-	(objectClass=*) sera utilis, ce qui corrspond 
-	une recherche de tous les types d'objets de l'arborescence. La
-	taille des filtres est limite  environ 8000 caractres (valeur
-	de la macro MAX_STRING_LEN dans le code source
-	d'Apache), ce qui s'avre plus que suffisant pour la plupart des
-	applications. Le mot-cl none permet de dsactiver
-	l'utilisation des filtres, ce qui peut s'avrer ncessaire avec
-	certains serveurs LDAP primitifs.
    
-
    
-
-    
    Pour une recherche, les attribut, filtre et nom d'utilisateur
-    fournis par le client HTTP sont combins pour crer un filtre de
-    recherche du style :
-    (&(filtre)(attribut
-    =nom-utilisateur)).
    
-
-    
    Par exemple, considrons l'URL
-    ldap://ldap.example.com/o=Example?cn?sub?(posixid=*).
-    Lorsqu'un client tentera de se connecter en utilisant le nom
-    d'utilisateur Babs Jenson, le filtre de recherche sera
-    : (&(posixid=*)(cn=Babs Jenson)).
    
-
-    
    On peut encore ajouter un paramtre optionnel pour permettre 
-    l'URL LDAP de surcharger le type de connexion. Ce paramtre peut
-    prendre l'une des valeurs suivantes :
    
-
-
    
-    
    NONE
    
-        
    tablit une connexion non scurise sur le port LDAP par
-	dfaut, ce qui est quivalent  ldap:// sur le port
-	389.
    
-    
    SSL
    
-        
    tablit une connexion scurise sur le port LDAP scuris
-	par dfaut, ce qui est quivalent  ldaps://.
    
-    
    TLS | STARTTLS
    
-        
    tablit une connexion scurise par lvation de niveau sur
-	le port LDAP par dfaut. Cette connexion sera initialise sur le
-	port 389 par dfaut, puis leve  un niveau de connexion
-	scurise sur le mme port.
    
-
    
-
-    
    Voir plus haut pour des exemples d'URLs dfinies par la directive
-    AuthLDAPURL.
    
-
-
    
-
    top
    
 
    
 
    Sommaire
    
 
@@ -1582,6 +885,703 @@ Require group     mygroupfile
    
       FrontPage.
     
 
+
+
    top
    
+
    Directive AuthLDAPAuthorizePrefix
    
+
+
+
+
+
+
+
+
+
+
    Description:Spcifie le prfixe ajout aux variables d'environnement
+durant la phase d'autorisation
    Syntaxe:AuthLDAPAuthorizePrefix prfixe
    Dfaut:AuthLDAPAuthorizePrefix AUTHORIZE_
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible depuis la version 2.3.6
    
+    
    Cette directive permet de spcifier le prfixe ajout aux
+    variables d'environnement durant la phase d'autorisation. Si la
+    valeur spcifie est AUTHENTICATE_, les utilisateurs de ces
+    variables d'environnement verront les mmes informations, que le
+    serveur effectue une authentification, une autorisation, ou les
+    deux.
    
+
+    
    Note
    
+    Aucune variable d'autorisation n'est dfinie lorsqu'un utilisateur
+    s'est vu autoriser l'accs via la directive Require
+    valid-user.
+    
    
+
+
    
+
    top
    
+
    Directive AuthLDAPBindAuthoritative
    
+
+
+
+
+
+
+
+
+
    Description:Dtermine si l'on doit utiliser d'autres fournisseurs
+d'authentification lorsque le serveur ne peut pas valider les donnes
+d'authentification de l'utilisateur, alors que ce dernier possde un
+DN.
    Syntaxe:AuthLDAPBindAuthoritativeoff|on
    Dfaut:AuthLDAPBindAuthoritative on
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
+    
    Par dfaut, des fournisseurs d'authentification sont appels
+    si un utilisateur ne possde pas de DN, mais ne le sont pas si
+    l'utilisateur possde un DN et si son mot de passe ne peut pas tre
+    vrifi lors d'une connexion au serveur LDAP. Si la directive
+    AuthLDAPBindAuthoritative est
+    dfinie  off, d'autres modules d'authentification
+    configurs auront une chance de valider le mot de passe de
+    l'utilisateur si la tentative de connexion au serveur LDAP choue
+    pour une raison quelconque (avec les donnes d'authentification
+    fournies).
    
+    
    Ceci permet aux utilisateurs prsent  la fois dans l'annuaire
+    LDAP et dans un fichier AuthUserFile de s'authentifier
+    lorsque le serveur LDAP est disponible, alors que le compte de
+    l'utilisateur est verrouill ou que son mot de passe est
+    inutilisable pour une raison quelconque.
    
+
+
    Voir aussi
    
+
+
    
+
    top
    
+
    Directive AuthLDAPBindDN
    
+
+
+
+
+
+
+
+
    Description:Un DN optionnel pour se connecter au serveur
+LDAP
    Syntaxe:AuthLDAPBindDN dn
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
+    
    Cette directive permet de dfinir un DN optionnel pour se
+    connecter au serveur afin d'y rechercher des entres. Si aucun DN
+    n'est spcifi, mod_authnz_ldap tentera une
+    connexion anonyme.
    
+
+
    
+
    top
    
+
    Directive AuthLDAPBindPassword
    
+
+
+
+
+
+
+
+
+
    Description:Mot de passe  utiliser en conjonction avec le DN de
+connexion
    Syntaxe:AuthLDAPBindPassword mot-de-passe
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:exec: est disponible depuis la version 2.4.5 du
+serveur HTTP Apache.
    
+    
    Cette directive permet de spcifier un mot de passe  utiliser en
+    conjonction avec le DN de connexion. Notez que ce mot de passe
+    constitue en gnral une donne sensible, et doit donc tre protg
+    de manire approprie. Vous ne devez utiliser les directives
+    AuthLDAPBindDN et AuthLDAPBindPassword que si
+    vous en avez vraiment besoin pour effectuer une recherche dans
+    l'annuaire.
    
+
+    
    Si la valeur commence par exec:, la commande rsultante sera
+    excute, et la premire ligne renvoye sur la sortie standard sera
+    utilise comme mot de passe.
    
+
    #Mot de passe utilis tel quel
+AuthLDAPBindPassword secret
+
+#Excute /path/to/program pour obtenir le mot de passe
+AuthLDAPBindPassword exec:/path/to/program
+
+#Excute /path/to/otherProgram avec un argument pour obtenir le mot de passe
+AuthLDAPBindPassword "exec:/path/to/otherProgram argument1"
    
+
+
+
+
    
+
    top
    
+
    Directive AuthLDAPCharsetConfig
    
+
+
+
+
+
+
+
    Description:Chemin du fichier de configuration de la correspondance
+langage/jeu de caractres
    Syntaxe:AuthLDAPCharsetConfig chemin-fichier
    Contexte:configuration du serveur
    Statut:Extension
    Module:mod_authnz_ldap
    
+    
    La directive AuthLDAPCharsetConfig permet
+    de dfinir le chemin du fichier de configuration de la
+    correspondance langage/jeu de caractres. chemin-fichier
+    est un chemin relatif au rpertoire dfini par la directive
+    ServerRoot. Ce fichier contient une liste
+    de correspondances extension de langage/jeu de caractres. La
+    plupart des administrateurs utilisent le fichier
+    charset.conv fourni qui associe les extensions de
+    langage courantes  leurs jeux de caractres.
    
+
+    
    Le fichier contient des lignes au format suivant :
    
+
+    
    
+      extension de langage jeu de caractres
+      [Nom du langage] ...
+    
    
+
+    
    L'extension est insensible  la casse. Les lignes vides et les
+    lignes commenant par un dise (#) sont ignores.
    
+
+
    
+
    top
    
+
    Directive AuthLDAPCompareAsUser
    
+
+
+
+
+
+
+
+
+
+
    Description:Utilisation des donnes d'authentification de l'utilisateur
+pour effectuer les comparaisons pour l'attribution des autorisations
    Syntaxe:AuthLDAPCompareAsUser on|off
    Dfaut:AuthLDAPCompareAsUser off
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible depuis la version version 2.3.6
    
+    
    Lorsque cette directive est dfinie, et si
+    mod_authnz_ldap a authentifi l'utilisateur, les
+    recherches LDAP pour les autorisations utilisent le nom distinctif
+    trouv (DN) et le mot de passe d'authentification basique HTTP de
+    l'utilisateur authentifi au lieu des donnes d'authentification
+    configures au niveau du serveur.
    
+
+    
    Les vrifications d'autorisation ldap-attribute,
+    ldap-user, et ldap-group (niveau simple seulement)
+    utilisent des comparaisons.
    
+
+    
    Cette directive n'a d'effet sur les comparaisons effectues au
+    cours des traitements de groupe imbriqus, et lorsque la directive
+    AuthLDAPSearchAsUser
+    est aussi active.
    
+
+    
    Cette directive ne doit tre utilise que si votre serveur LDAP
+     n'autorise pas les recherches anonymes, ou si vous ne pouvez pas
+     utiliser de nom d'utilisateur ddi via la directive AuthLDAPBindDN.
+     
    
+
+
    Voir aussi
    
+
+
    
+
    top
    
+
    Directive AuthLDAPCompareDNOnServer
    
+
+
+
+
+
+
+
+
+
    Description:Utilise le serveur LDAP pour comparer les DNs
    Syntaxe:AuthLDAPCompareDNOnServer on|off
    Dfaut:AuthLDAPCompareDNOnServer on
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
+    
    Lorsque cette directive est dfinie  on,
+    mod_authnz_ldap utilise le serveur LDAP pour
+    comparer les DNs. Il s'agit de la seule mthode infaillible pour
+    comparer les DNs. mod_authnz_ldap va rechercher
+    dans l'annuaire le DN spcifi par la directive Require dn, puis extraire ce DN et le
+    comparer avec le DN extrait de l'entre de l'utilisateur. Si cette
+    directive est  off, mod_authnz_ldap effectue une
+    simple comparaison de chanes. Cette dernire approche peut produire
+    des faux ngatifs, mais elle est beaucoup plus rapide. Notez
+    cependant que le cache de mod_ldap peut acclrer
+    la comparaison de DNs dans la plupart des situations.
    
+
+
    
+
    top
    
+
    Directive AuthLDAPDereferenceAliases
    
+
+
+
+
+
+
+
+
+
    Description: quel moment le module va drfrencer les
+alias
    Syntaxe:AuthLDAPDereferenceAliases never|searching|finding|always
    Dfaut:AuthLDAPDereferenceAliases always
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
+    
    Cette directive permet de spcifier  quel moment
+    mod_authnz_ldap va drfrencer les alias au cours
+    des oprations lies  LDAP. La valeur par dfaut est
+    always.
    
+
+
    
+
    top
    
+
    Directive AuthLDAPGroupAttribute
    
+
+
+
+
+
+
+
+
+
    Description:L'attribut LDAP utilis pour vrifier l'appartenance d'un
+utilisateur  un groupe.
    Syntaxe:AuthLDAPGroupAttribute attribut
    Dfaut:AuthLDAPGroupAttribute member uniquemember
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
+    
    Cette directive permet de spcifier quel attribut LDAP est
+    utilis pour vrifier l'appartenance d'un utilisateur  un
+    groupe. On peut spcifier plusieurs attributs en rptant cette
+    directive plusieurs fois. Si la directive n'est pas dfinie,
+    mod_authnz_ldap utilise les attributs
+    member et uniquemember.
    
+
+
    
+
    top
    
+
    Directive AuthLDAPGroupAttributeIsDN
    
+
+
+
+
+
+
+
+
+
    Description:Utilise le DN de l'utilisateur pour vrifier son
+appartenance  un groupe
    Syntaxe:AuthLDAPGroupAttributeIsDN on|off
    Dfaut:AuthLDAPGroupAttributeIsDN on
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
+    
    Lorsqu'elle est dfinie  on, cette directive
+    indique que c'est le DN de l'utilisateur qui doit tre utilis pour
+    vrifier son appartenance  un groupe. Dans le cas contraire, c'est
+    le nom de l'utilisateur qui sera utilis. Par exemple, supposons que
+    le client envoie le nom d'utilisateur bjenson, qui
+    correspond au DN LDAP cn=Babs Jenson,o=Example. Si la
+    directive est  on, mod_authnz_ldap va
+    vrifier si cn=Babs Jenson, o=Example est un membre du
+    groupe. Dans le cas contraire, mod_authnz_ldap
+    vrifiera si bjenson est un membre du groupe.
    
+
+
    
+
    top
    
+
    Directive AuthLDAPInitialBindAsUser
    
+
+
+
+
+
+
+
+
+
+
    Description:Dtermine si le serveur effectue la recherche initiale du
+DN en utilisant le nom propre de l'utilisateur pour l'authentification
+de base
+et non de manire anonyme, ou en utilisant des donnes d'authentification
+codes en dur pour le serveur
    Syntaxe:AuthLDAPInitialBindAsUser off|on
    Dfaut:AuthLDAPInitialBindAsUser off
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible depuis la version 2.3.6
    
+    
    Par dfaut, le serveur convertit le nom d'utilisateur pour
+    l'authentification de base en nom distinctif LDAP (DN) soit de
+    manire anonyme, soit avec un couple nom/mot de passe ddi. Cette
+    directive permet de forcer le serveur  utiliser les vritables nom
+    d'utilisateur et mot de passe fournis par l'utilisateur pour
+    effectuer la recherche initiale du DN.
    
+
+     
    Si le nom d'utilisateur ne peut pas s'authentifier directement
+     et ncessite de lgres modifications, voir la directive AuthLDAPInitialBindPattern.
    
+
+     
    Cette directive ne doit tre utilise que si votre serveur LDAP
+     n'autorise pas les recherches anonymes, ou si vous ne pouvez pas
+     utiliser de nom d'utilisateur ddi via la directive AuthLDAPBindDN.
+     
    
+
+     
    Non disponible dans la cas d'une autorisation seule
    
+         On ne peut utiliser cette directive que si ce module
+	 effectue une authentification, et n'a aucun effet si ce module
+	 n'est utilis que pour les processus d'autorisation.
+     
    
+
+
    Voir aussi
    
+
+
    
+
    top
    
+
    Directive AuthLDAPInitialBindPattern
    
+
+
+
+
+
+
+
+
+
+
    Description:Spcifie la modification a apporter au nom d'utilisateur
+pour l'authentification de base lors de l'authentification auprs du
+serveur LDAP pour effectuer une recherche de DN
    Syntaxe:AuthLDAPInitialBindPatternregex substitution
    Dfaut:AuthLDAPInitialBindPattern (.*) $1 (nom de l'utilisateur
+distant utilis tel quel)
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible depuis la version 2.3.6
    
+    
    Si la directive AuthLDAPInitialBindAsUser est
+    dfinie  ON, le nom utilisateur pour l'authentification de
+    base sera transform selon l'expression rationnelle
+    regex et l'argument substitution spcifis.
    
+
+    
    L'expression rationnelle est compare au nom d'utilisateur pour
+    l'authentification de base courant. L'argument
+    substitution peut contenir des rfrences arrires, mais
+    n'effectue aucune autre interpolation de variable.
    
+
+    
    Cette directive ne doit tre utilise que si votre serveur LDAP
+     n'autorise pas les recherches anonymes, ou si vous ne pouvez pas
+     utiliser de nom d'utilisateur ddi via la directive AuthLDAPBindDN.
+     
    
+
+    
    AuthLDAPInitialBindPattern (.+) $1@example.com
    
+
+    
    AuthLDAPInitialBindPattern (.+) cn=$1,dc=example,dc=com
    
+
+
+    
    Non disponible dans la cas d'une autorisation seule
    
+         On ne peut utiliser cette directive que si ce module
+	 effectue une authentification, et n'a aucun effet si ce module
+	 n'est utilis que pour les processus d'autorisation.
+     
    
+    
    Dbogage
    
+        Le DN de substitution est enregistr dans la variable
+	d'environnement LDAP_BINDASUSER. Si l'expression
+	rationnelle ne convient pas, le nom d'utilisateur est utilis
+	tel quel.
+    
    
+
+
    Voir aussi
    
+
+
    
+
    top
    
+
    Directive AuthLDAPMaxSubGroupDepth
    
+
+
+
+
+
+
+
+
+
+
    Description:Spcifie la profondeur d'imbrication des sous-groupes
+maximale prise en compte avant l'abandon de la recherche de
+l'utilisateur.
    Syntaxe:AuthLDAPMaxSubGroupDepth Nombre
    Dfaut:AuthLDAPMaxSubGroupDepth 0
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible  partir de la version 2.3.0 du serveur HTTP
+Apache ; la valeur par dfaut tait 10 dans les versions 2.4.x et les
+premires versions 2.5
    
+   
    Lorsque cette directive est dfinie  une valeur X
+   non nulle, en combinaison avec l'utilisation de la directive
+   Require ldap-group DN-groupe, les donnes de connexion
+   fournies seront utilises pour vrifier l'appartenance de
+   l'utilisateur  l'objet de l'annuaire DN-groupe ou 
+   tout sous-groupe du groupe courant en tenant compte de la profondeur
+   d'imbrication maximale X spcifie par la directive.
    
+   
    Se rfrer  la section Require
+   ldap-group pour un exemple plus dtaill.
    
+
+   
    Performances dans le cas des groupes imbriqus
    
+   
    Lorsque les directives
+   AuthLDAPSubGroupAttribute et
+   AuthLDAPGroupAttribute se recouvrent (comme
+   c'est le cas par dfaut et requis par les schmas LDAP courants), la
+   recherche de sous-groupes au sein de grands groupes peut tre trs
+   longue. Si vos groupes sont trs grands et non imbriqus, dfinissez
+   la directive AuthLDAPMaxSubGroupDepth  0.
    
+   
    
+
+
+
    
+
    top
    
+
    Directive AuthLDAPRemoteUserAttribute
    
+
+
+
+
+
+
+
+
+
    Description:Spcifie l'attribut dont la valeur renvoye au cours de la
+requte de l'utilisateur sera utilise pour dfinir la variable
+d'environnement REMOTE_USER
    Syntaxe:AuthLDAPRemoteUserAttribute uid
    Dfaut:none
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
+    
    Lorsque cette directive est dfinie, la variable d'environnement
+    REMOTE_USER sera dfinie  la valeur de l'attribut
+    spcifi. Assurez-vous que cet attribut soit bien inclus dans la
+    liste d'attributs spcifis dans la dfinition de AuthLDAPUrl ; dans
+    le cas contraire, cette directive n'aurait aucun effet. Si elle est
+    prsente, cette directive l'emporte sur AuthLDAPRemoteUserIsDN. Elle
+    peut s'avrer utile par exemple, si vous souhaitez que les
+    utilisateurs se connectent  un site web en utilisant leur adresse
+    email, alors qu'une application sous-jacente ncessite un nom
+    d'utilisateur comme identifiant.
    
+    
    Cette directive n'a d'effet que si l'on utilise ce module pour
+    l'authentification.
    
+
+
    
+
    top
    
+
    Directive AuthLDAPRemoteUserIsDN
    
+
+
+
+
+
+
+
+
+
    Description:Utilise le DN de l'utilisateur pour dfinir la variable
+d'environnement REMOTE_USER
    Syntaxe:AuthLDAPRemoteUserIsDN on|off
    Dfaut:AuthLDAPRemoteUserIsDN off
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
+    
    Lorsque cette directive est  on, la variable d'environnement
+    REMOTE_USER sera dfinie avec la valeur du DN complet
+    de l'utilisateur authentifi, et non plus avec simplement le nom
+    d'utilisateur fourni par le client. Elle est dfinie  off par
+    dfaut.
    
+    
    Cette directive n'a d'effet que si l'on utilise ce module pour
+    l'authentification.
    
+
+
    
+
    top
    
+
    Directive AuthLDAPSearchAsUser
    
+
+
+
+
+
+
+
+
+
+
    Description:Utilise les donnes d'authentification de l'utilisateur
+pour la recherche des autorisations
    Syntaxe:AuthLDAPSearchAsUser on|off
    Dfaut:AuthLDAPSearchAsUser off
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible depuis la version 2.3.6
    
+    
    Lorsque cette directive est dfinie, et si
+    mod_authnz_ldap a authentifi l'utilisateur, les
+    recherches LDAP pour dfinir les autorisations utilisent le nom
+    distinctif (DN) trouv et le mot de passe pour l'authentification de
+    base HTTP de l'utilisateur authentifi, au lieu des donnes
+    d'authentification configures au niveau du serveur.
    
+
+    
    Les vrifications d'autorisation ldap-filter et
+    ldap-dn utilisent des recherches.
    
+
+    
    Cette directive n'a d'effet sur les comparaisons effectues au
+    cours des traitements de groupe imbriqus, et lorsque la directive
+    AuthLDAPCompareAsUser
+    est aussi active.
    
+
+     
    Cette directive ne doit tre utilise que si votre serveur LDAP
+     n'autorise pas les recherches anonymes, ou si vous ne pouvez pas
+     utiliser de nom d'utilisateur ddi via la directive AuthLDAPBindDN.
+     
    
+
+
+
    Voir aussi
    
+
+
    
+
    top
    
+
    Directive AuthLDAPSubGroupAttribute
    
+
+
+
+
+
+
+
+
+
+
    Description:Spcifie les noms d'attribut, un par directive, utiliss
+pour diffrencier les membres du groupe courant qui sont eux-mmes des
+groupes.
    Syntaxe:AuthLDAPSubGroupAttribute attribut
    Dfaut:AuthLDAPSubgroupAttribute member uniquemember
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible  partir de la version 2.3.0 du serveur HTTP
+Apache
    
+    
    Un objet groupe LDAP peut contenir des membres qui sont des
+    utilisateurs et des membres qui sont eux-mmes des groupes (appels
+    sous-groupes ou groupes imbriqus). La directive
+    AuthLDAPSubGroupAttribute spcifie l'attribut utilis
+    pour identifier les groupes, alors que la directive
+    AuthLDAPGroupAttribute spcifie l'attribut utilis
+    pour identifier les utilisateurs. On peut spcifier plusieurs
+    attributs en rptant la directive plusieurs fois. Si elle n'est pas
+    dfinie, mod_authnz_ldap utilise les attributs
+    member et uniqueMember.
    
+
+
    
+
    top
    
+
    Directive AuthLDAPSubGroupClass
    
+
+
+
+
+
+
+
+
+
+
    Description:Spcifie quelles valeurs d'objectClass LDAP identifient les
+objets de l'annuaire qui sont des groupes au cours du traitement des
+sous-groupes.
    Syntaxe:AuthLDAPSubGroupClass ObjectClass-LDAP
    Dfaut:AuthLDAPSubGroupClass groupOfNames groupOfUniqueNames
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    Compatibilit:Disponible  partir de la version 2.3.0 du serveur HTTP
+Apache
    
+    
    Un objet groupe LDAP peut contenir des membres qui sont des
+    utilisateurs et des membres qui sont eux-mmes des groupes (appels
+    sous-groupes ou groupes imbriqus). La directive
+    AuthLDAPSubGroupAttribute permet d'identifier les
+    membres qui sont des sous-groupes du groupe courant ( l'oppos des
+    membres utilisateurs). La directive
+    AuthLDAPSubGroupClass permet de spcifier les valeurs
+    d'objectClass LDAP utilises pour vrifier que certains membres sont
+    en fait des objets groupe. Les sous-groupes ainsi identifis peuvent
+    alors faire l'objet d'une recherche d'autres membres utilisateurs ou
+    sous-groupes. On peut spcifier plusieurs attributs en rptant
+    cette directive plusieurs fois. Si cette directive n'est pas
+    dfinie, mod_authnz_ldap utilise les attributs
+    groupOfNames et groupOfUniqueNames.
    
+
+
    
+
    top
    
+
    Directive AuthLDAPUrl
    
+
+
+
+
+
+
+
+
    Description:L'URL permettant de spcifier les paramtres de la
+recherche LDAP
    Syntaxe:AuthLDAPUrl url [NONE|SSL|TLS|STARTTLS]
    Contexte:rpertoire, .htaccess
    AllowOverride:AuthConfig
    Statut:Extension
    Module:mod_authnz_ldap
    
+    
    Une URL conforme  la RFC 2255 qui permet de spcifier les
+    paramtres  utiliser pour la recherche dans l'annuaire LDAP. La
+    syntaxe de l'URL est :
    
+
    ldap://hte:port/DN-de-base?attribut?porte?filtre
    
+    
    Si vous souhaitez mettre  la disposition d'Apache plusieurs URLs
+    LDAP, la syntaxe sera :
    
+
    AuthLDAPUrl "ldap://ldap1.example.com ldap2.example.com/dc=..."
    
+
+
    Mise en garde : Si vous spcifiez plusieurs
+serveurs, vous devez en entourer la liste avec des guillemets ; dans le
+cas contraire, vous gnrerez une erreur : "AuthLDAPURL takes one
+argument, URL to define LDAP connection..". Vous pouvez bien
+entendu ajouter des paramtres de recherche  chacun des serveurs
+spcifis.
    
+
+
    
+
    ldap
    
+
+        
    Pour ldap non scuris, utilisez la chane
+	ldap. Pour ldap scuris, utilisez  la place la
+	chane ldaps. LDAP scuris n'est disponible que si
+	Apache a t li avec une bibliothque LDAP supportant SSL.
    
+
+
    hte:port
    
+
+        
    
+          
    Il s'agit du nom/port du serveur ldap
+	  (dont la valeur par dfaut est
+	  localhost:389 pour ldap, et
+	  localhost:636 pour ldaps). Pour
+	  spcifier plusieurs serveurs LDAP redondants, indiquez
+	  simplement leur liste en les sparant par des espaces.
+	  mod_authnz_ldap tentera alors de se connecter
+	   chacun des serveurs jusqu' ce qu'il parvienne  se
+	  connecter avec succs. Notez qu'en cas de multiples serveurs
+	  LDAP, l'ensemble de l'URL LDAP doit tre entoure de
+	  guillemets.
    
+
+          
    lorsqu'une connection a t tablie avec un serveur, elle
+	  reste active pendant toute la dure de vie du processus
+	  httpd, ou jusqu' ce que le serveur LDAP
+	  cesse de fonctionner.
    
+
+          
    Si le serveur LDAP cesse de fonctionner, et ainsi
+	  interrompt une
+	  connexion existante, mod_authnz_ldap tentera
+	  de se reconnecter en commenant par le premier serveur de la
+	  liste, et ainsi de suite avec les serveurs redondants
+	  suivants. Notez que ce processus n'a rien  voir avec une
+	  vritable recherche de type round-robin.
    
+        
    
+
+
    DN-de-base
    
+        
    Le DN de la branche de l'annuaire  partir de laquelle
+	toutes les recherches seront lances. Il doit au moins
+	correspondre  la racine de votre annuaire, mais vous pouvez
+	aussi indiquer une branche plus spcifique.
    
+
+
    attribut
    
+
+        
    Il s'agit de l'attribut  utiliser pour la recherche.
+	Bien que la RFC
+	2255 autorise une liste d'attributs spars par des virgules,
+	seul le premier sera retenu, sans tenir compte des autres
+	attributs fournis. Si aucun attribut n'est fourni, l'attribut
+	par dfaut est uid. Il est judicieux de choisir un
+	attribut dont la valeur sera unique parmi toutes les entres de
+	la branche de l'annuaire que vous aurez dfinie. Tous les
+	attributs spcifis seront enregistrs dans des variables
+	d'environnement avec le prfixe AUTHENTICATE_, afin de pouvoir
+	tre utiliss par d'autres modules.
    
+
+
    porte
    
+
+        
    Il s'agit de la porte de la recherche. Elle peut prendre
+	les valeurs one ou sub. Notez que la
+	RFC 2255 supporte aussi une porte de valeur base,
+	mais cette dernire n'est pas supporte par le module. Si la
+	porte n'est pas dfinie, ou si elle est dfinie 
+	base, c'est la valeur de porte par dfaut
+	sub qui sera utilise.
    
+
+
    filtre
    
+
+        
    Il s'agit d'un filtre de recherche LDAP valide. Si aucun
+	filtre n'est spcifi, le filtre par dfaut
+	(objectClass=*) sera utilis, ce qui corrspond 
+	une recherche de tous les types d'objets de l'arborescence. La
+	taille des filtres est limite  environ 8000 caractres (valeur
+	de la macro MAX_STRING_LEN dans le code source
+	d'Apache), ce qui s'avre plus que suffisant pour la plupart des
+	applications. Le mot-cl none permet de dsactiver
+	l'utilisation des filtres, ce qui peut s'avrer ncessaire avec
+	certains serveurs LDAP primitifs.
    
+
    
+
+    
    Pour une recherche, les attribut, filtre et nom d'utilisateur
+    fournis par le client HTTP sont combins pour crer un filtre de
+    recherche du style :
+    (&(filtre)(attribut
+    =nom-utilisateur)).
    
+
+    
    Par exemple, considrons l'URL
+    ldap://ldap.example.com/o=Example?cn?sub?(posixid=*).
+    Lorsqu'un client tentera de se connecter en utilisant le nom
+    d'utilisateur Babs Jenson, le filtre de recherche sera
+    : (&(posixid=*)(cn=Babs Jenson)).
    
+
+    
    On peut encore ajouter un paramtre optionnel pour permettre 
+    l'URL LDAP de surcharger le type de connexion. Ce paramtre peut
+    prendre l'une des valeurs suivantes :
    
+
+
    
+    
    NONE
    
+        
    tablit une connexion non scurise sur le port LDAP par
+	dfaut, ce qui est quivalent  ldap:// sur le port
+	389.
    
+    
    SSL
    
+        
    tablit une connexion scurise sur le port LDAP scuris
+	par dfaut, ce qui est quivalent  ldaps://.
    
+    
    TLS | STARTTLS
    
+        
    tablit une connexion scurise par lvation de niveau sur
+	le port LDAP par dfaut. Cette connexion sera initialise sur le
+	port 389 par dfaut, puis leve  un niveau de connexion
+	scurise sur le mme port.
    
+
    
+
+    
    Voir plus haut pour des exemples d'URLs dfinies par la directive
+    AuthLDAPURL.
    
+
 
    
 
 
    
diff --git a/docs/manual/mod/mod_authz_core.html.en b/docs/manual/mod/mod_authz_core.html.en
index 490563ef39..a9eb23b231 100644
--- a/docs/manual/mod/mod_authz_core.html.en
+++ b/docs/manual/mod/mod_authz_core.html.en
@@ -61,6 +61,210 @@
 
 
    
 
    top
    
+
    
+
    Authorization Containers
    
+
+    
    The authorization container directives
+    <RequireAll>,
+    <RequireAny>
+    and
+    <RequireNone>
+    may be combined with each other and with the
+    Require
+    directive to express complex authorization logic.
    
+
+    
    The example below expresses the following authorization logic.
+    In order to access the resource, the user must either be the
+    superadmin user, or belong to both the
+    admins group and the Administrators LDAP
+    group and either belong to the sales group or
+    have the LDAP dept attribute sales.
+    Furthermore, in order to access the resource, the user must
+    not belong to either the temps group or the
+    LDAP group Temporary Employees.
    
+
+    
    <Directory "/www/mydocs">
+    <RequireAll>
+        <RequireAny>
+            Require user superadmin
+            <RequireAll>
+                Require group admins
+                Require ldap-group "cn=Administrators,o=Airius"
+                <RequireAny>
+                    Require group sales
+                    Require ldap-attribute dept="sales"
+                </RequireAny>
+            </RequireAll>
+        </RequireAny>
+        <RequireNone>
+            Require group temps
+            Require ldap-group "cn=Temporary Employees,o=Airius"
+        </RequireNone>
+    </RequireAll>
+</Directory>
    
+
+
    top
    
+
    
+
    The Require Directives
    
+
+  
    mod_authz_core provides some generic authorization
+  providers which can be used with the
+  Require directive.
    
+
+  
    Require env
    
+
+    
    The env provider allows access to the server
+    to be controlled based on the existence of an environment variable. When Require
+    env env-variable is specified, then the request is
+    allowed access if the environment variable env-variable
+    exists. The server provides the ability to set environment
+    variables in a flexible way based on characteristics of the client
+    request using the directives provided by
+    mod_setenvif. Therefore, this directive can be
+    used to allow access based on such factors as the clients
+    User-Agent (browser type), Referer, or
+    other HTTP request header fields.
    
+
+    
    SetEnvIf User-Agent "^KnockKnock/2\.0" let_me_in
+<Directory "/docroot">
+    Require env let_me_in
+</Directory>
    
+
+
+    
    In this case, browsers with a user-agent string beginning
+    with KnockKnock/2.0 will be allowed access, and all
+    others will be denied.
    
+
+    
    When the server looks up a path via an internal 
+    subrequest such as looking 
+    for a DirectoryIndex 
+    or generating a directory listing with mod_autoindex,
+    per-request environment variables are not inherited in the 
+    subrequest. Additionally, 
+    SetEnvIf directives
+    are not separately evaluated in the subrequest due to the API phases
+    mod_setenvif takes action in.
    
+
+  
+
+  
    Require all
    
+
+    
    The all provider mimics the functionality that
+    was previously provided by the 'Allow from all' and 'Deny from all'
+    directives.  This provider can take one of two arguments which are
+    'granted' or 'denied'.  The following examples will grant or deny
+    access to all requests.
    
+
+    
    Require all granted
    
+
+
+    
    Require all denied
    
+
+
+  
+
+  
    Require method
    
+
+    
    The method provider allows using the HTTP method in
+    authorization decisions. The GET and HEAD methods are treated as
+    equivalent. The TRACE method is not available to this provider,
+    use TraceEnable instead.
    
+
+    
    The following example will only allow GET, HEAD, POST, and OPTIONS
+    requests:
    
+
+    
    Require method GET POST OPTIONS
    
+
+
+    
    The following example will allow GET, HEAD, POST, and OPTIONS
+    requests without authentication, and require a valid user for all other
+    methods:
    
+
+    
    <RequireAny>
+    Require method GET POST OPTIONS
+    Require valid-user
+</RequireAny>
    
+
+
+  
+
+  
    Require expr
    
+
+  
    The expr provider allows basing authorization
+  decisions on arbitrary expressions.
    
+
+    
    Require expr %{TIME_HOUR} -ge 9 && %{TIME_HOUR} -le 17
    
+
+
+    
    <RequireAll>
+    Require expr "!(%{QUERY_STRING} =~ /secret/)"
+    Require expr "%{REQUEST_URI} in { '/example.cgi', '/other.cgi' }" 
+</RequireAll>
    
+
+
+    
    Require expr "!(%{QUERY_STRING} =~ /secret/) && %{REQUEST_URI} in { '/example.cgi', '/other.cgi' }"
    
+
+
+  
    The syntax is described in the ap_expr
+  documentation.
    
+
+  
    Normally, the expression is evaluated before authentication. However, if
+  the expression returns false and references the variable
+  %{REMOTE_USER}, authentication will be performed and
+  the expression will be re-evaluated.
    
+
+  
+
+
+
    top
    
+
    
+
    Creating Authorization Provider Aliases
    
+
+    
    Extended authorization providers can be created within the configuration
+    file and assigned an alias name.  The alias providers can then be referenced
+    through the Require directive
+    in the same way as a base authorization provider.  Besides the ability to
+    create and alias an extended provider, it also allows the same extended
+    authorization provider to be referenced by multiple locations.
+    
    
+
+    
    Example
    
+        
    The example below creates two different ldap authorization provider
+        aliases based on the ldap-group authorization provider.  This example
+        allows a single authorization location to check group membership within
+        multiple ldap hosts:
+        
    
+
+        
    <AuthzProviderAlias ldap-group ldap-group-alias1 "cn=my-group,o=ctx">
+    AuthLDAPBindDN "cn=youruser,o=ctx"
+    AuthLDAPBindPassword yourpassword
+    AuthLDAPURL "ldap://ldap.host/o=ctx"
+</AuthzProviderAlias>
+
+<AuthzProviderAlias ldap-group ldap-group-alias2 "cn=my-other-group,o=dev">
+    AuthLDAPBindDN "cn=yourotheruser,o=dev"
+    AuthLDAPBindPassword yourotherpassword
+    AuthLDAPURL "ldap://other.ldap.host/o=dev?cn"
+</AuthzProviderAlias>
+
+Alias "/secure" "/webpages/secure"
+<Directory "/webpages/secure">
+    Require all granted
+
+    AuthBasicProvider file
+
+    AuthType Basic
+    AuthName LDAP_Protected_Place
+
+    #implied OR operation
+    Require ldap-group-alias1
+    Require ldap-group-alias2
+</Directory>
    
+
+    
+
+
    
+
    top
    
 
    AuthMerging Directive
    
 
  • Authentication, Authorization,
     and Access Control
    • 
-
-
    top
    
-
    
-
    Authorization Containers
    
-
-    
    The authorization container directives
-    <RequireAll>,
-    <RequireAny>
-    and
-    <RequireNone>
-    may be combined with each other and with the
-    Require
-    directive to express complex authorization logic.
    
-
-    
    The example below expresses the following authorization logic.
-    In order to access the resource, the user must either be the
-    superadmin user, or belong to both the
-    admins group and the Administrators LDAP
-    group and either belong to the sales group or
-    have the LDAP dept attribute sales.
-    Furthermore, in order to access the resource, the user must
-    not belong to either the temps group or the
-    LDAP group Temporary Employees.
    
-
-    
    <Directory "/www/mydocs">
-    <RequireAll>
-        <RequireAny>
-            Require user superadmin
-            <RequireAll>
-                Require group admins
-                Require ldap-group "cn=Administrators,o=Airius"
-                <RequireAny>
-                    Require group sales
-                    Require ldap-attribute dept="sales"
-                </RequireAny>
-            </RequireAll>
-        </RequireAny>
-        <RequireNone>
-            Require group temps
-            Require ldap-group "cn=Temporary Employees,o=Airius"
-        </RequireNone>
-    </RequireAll>
-</Directory>
    
-
-
    top
    
-
    
-
    The Require Directives
    
-
-  
    mod_authz_core provides some generic authorization
-  providers which can be used with the
-  Require directive.
    
-
-  
    Require env
    
-
-    
    The env provider allows access to the server
-    to be controlled based on the existence of an environment variable. When Require
-    env env-variable is specified, then the request is
-    allowed access if the environment variable env-variable
-    exists. The server provides the ability to set environment
-    variables in a flexible way based on characteristics of the client
-    request using the directives provided by
-    mod_setenvif. Therefore, this directive can be
-    used to allow access based on such factors as the clients
-    User-Agent (browser type), Referer, or
-    other HTTP request header fields.
    
-
-    
    SetEnvIf User-Agent "^KnockKnock/2\.0" let_me_in
-<Directory "/docroot">
-    Require env let_me_in
-</Directory>
    
-
-
-    
    In this case, browsers with a user-agent string beginning
-    with KnockKnock/2.0 will be allowed access, and all
-    others will be denied.
    
-
-    
    When the server looks up a path via an internal 
-    subrequest such as looking 
-    for a DirectoryIndex 
-    or generating a directory listing with mod_autoindex,
-    per-request environment variables are not inherited in the 
-    subrequest. Additionally, 
-    SetEnvIf directives
-    are not separately evaluated in the subrequest due to the API phases
-    mod_setenvif takes action in.
    
-
-  
-
-  
    Require all
    
-
-    
    The all provider mimics the functionality that
-    was previously provided by the 'Allow from all' and 'Deny from all'
-    directives.  This provider can take one of two arguments which are
-    'granted' or 'denied'.  The following examples will grant or deny
-    access to all requests.
    
-
-    
    Require all granted
    
-
-
-    
    Require all denied
    
-
-
-  
-
-  
    Require method
    
-
-    
    The method provider allows using the HTTP method in
-    authorization decisions. The GET and HEAD methods are treated as
-    equivalent. The TRACE method is not available to this provider,
-    use TraceEnable instead.
    
-
-    
    The following example will only allow GET, HEAD, POST, and OPTIONS
-    requests:
    
-
-    
    Require method GET POST OPTIONS
    
-
-
-    
    The following example will allow GET, HEAD, POST, and OPTIONS
-    requests without authentication, and require a valid user for all other
-    methods:
    
-
-    
    <RequireAny>
-    Require method GET POST OPTIONS
-    Require valid-user
-</RequireAny>
    
-
-
-  
-
-  
    Require expr
    
-
-  
    The expr provider allows basing authorization
-  decisions on arbitrary expressions.
    
-
-    
    Require expr %{TIME_HOUR} -ge 9 && %{TIME_HOUR} -le 17
    
-
-
-    
    <RequireAll>
-    Require expr "!(%{QUERY_STRING} =~ /secret/)"
-    Require expr "%{REQUEST_URI} in { '/example.cgi', '/other.cgi' }" 
-</RequireAll>
    
-
-
-    
    Require expr "!(%{QUERY_STRING} =~ /secret/) && %{REQUEST_URI} in { '/example.cgi', '/other.cgi' }"
    
-
-
-  
    The syntax is described in the ap_expr
-  documentation.
    
-
-  
    Normally, the expression is evaluated before authentication. However, if
-  the expression returns false and references the variable
-  %{REMOTE_USER}, authentication will be performed and
-  the expression will be re-evaluated.
    
-
-  
-
-
-
    top
    
-
    
-
    Creating Authorization Provider Aliases
    
-
-    
    Extended authorization providers can be created within the configuration
-    file and assigned an alias name.  The alias providers can then be referenced
-    through the Require directive
-    in the same way as a base authorization provider.  Besides the ability to
-    create and alias an extended provider, it also allows the same extended
-    authorization provider to be referenced by multiple locations.
-    
    
-
-    
    Example
    
-        
    The example below creates two different ldap authorization provider
-        aliases based on the ldap-group authorization provider.  This example
-        allows a single authorization location to check group membership within
-        multiple ldap hosts:
-        
    
-
-        
    <AuthzProviderAlias ldap-group ldap-group-alias1 "cn=my-group,o=ctx">
-    AuthLDAPBindDN "cn=youruser,o=ctx"
-    AuthLDAPBindPassword yourpassword
-    AuthLDAPURL "ldap://ldap.host/o=ctx"
-</AuthzProviderAlias>
-
-<AuthzProviderAlias ldap-group ldap-group-alias2 "cn=my-other-group,o=dev">
-    AuthLDAPBindDN "cn=yourotheruser,o=dev"
-    AuthLDAPBindPassword yourotherpassword
-    AuthLDAPURL "ldap://other.ldap.host/o=dev?cn"
-</AuthzProviderAlias>
-
-Alias "/secure" "/webpages/secure"
-<Directory "/webpages/secure">
-    Require all granted
-
-    AuthBasicProvider file
-
-    AuthType Basic
-    AuthName LDAP_Protected_Place
-
-    #implied OR operation
-    Require ldap-group-alias1
-    Require ldap-group-alias2
-</Directory>
    
-
-    
-
 
    
diff --git a/docs/manual/mod/mod_authz_core.html.fr b/docs/manual/mod/mod_authz_core.html.fr
index 0374e8c3cc..c51e596dc3 100644
--- a/docs/manual/mod/mod_authz_core.html.fr
+++ b/docs/manual/mod/mod_authz_core.html.fr
@@ -47,7 +47,13 @@ d'Apache HTTPD
    
 
    Description:Controls the manner in which each configuration section's
@@ -427,210 +631,6 @@ must succeed for the enclosing directive to not fail.
    
 
 
 
 
    
     permet aussi l'application d'une logique labore au droulement du
     processus d'autorisation.
    
 
    
-
+
    top
    
+
    
+
    Conteneurs d'autorisation
    
+
+    
    Les directives de conteneur d'autorisation <RequireAll>,
+    <RequireAny> et <RequireNone>
+    peuvent tre combines entre elles et avec la directive Require pour construire une
+    logique d'autorisation complexe.
    
+
+    
    L'exemple ci-dessous illustre la logique d'autorisation suivante.
+    Pour pouvoir accder  la ressource, l'utilisateur doit tre
+    l'utilisateur superadmin, ou appartenir aux deux
+    groupes LDAP admins et Administrateurs et
+    soit appartenir au groupe ventes, soit avoir
+    ventes comme valeur de l'attribut LDAP
+    dept. De plus, pour pouvoir accder  la ressource,
+    l'utilisateur ne doit appartenir ni au groupe temps, ni
+    au groupe LDAP Employs temporaires.
    
+
+    
    <Directory /www/mydocs>
+    <RequireAll>
+        <RequireAny>
+            Require user superadmin
+            <RequireAll>
+            Require group admins
+            Require ldap-group cn=Administrateurs,o=Airius
+                <RequireAny>
+                Require group ventes
+                Require ldap-attribute dept="ventes"
+                </RequireAny>
+            </RequireAll>
+        </RequireAny>
+        <RequireNone>
+            Require group temps
+            Require ldap-group cn=Employs temporaires,o=Airius
+        </RequireNone>
+    </RequireAll>
+</Directory>
    
+
+
    top
    
+
    
+
    Les directives Require
    
+
+  
    Le module mod_authz_core met  disposition des
+  fournisseurs d'autorisation gnriques utilisables avec la directive
+  Require.
    
+
+  
    Require env
    
+
+    
    Le fournisseur env permet de contrler l'accs au
+    serveur en fonction de l'existence d'une variable d'environnement. Lorsque Require
+    env env-variable est spcifi, la requte se voit
+    autoriser l'accs si la variable d'environnement
+    env-variable existe. Le serveur permet de dfinir
+    facilement des variables d'environnement en fonction des
+    caractristiques de la requte du client via les directives fournies
+    par le module mod_setenvif. Cette directive Require
+    env permet donc de contrler l'accs en fonction des
+    valeurs des en-ttes de la requte HTTP tels que
+    User-Agent (type de navigateur), Referer,
+    entre autres.
    
+
+    
    SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in
+<Directory /docroot>
+    Require env let_me_in
+</Directory>
    
+
+
+    
    Avec cet exemple, les navigateurs dont la chane user-agent
+    commence par KnockKnock/2.0 se verront autoriser
+    l'accs, alors que tous les autres seront rejets.
    
+
+    
    Lorsque le serveur cherche un chemin via une sous-requte interne (par exemple la
+   recherche d'un DirectoryIndex), ou lorsqu'il gnre un
+   listing du contenu d'un rpertoire via le module
+   mod_autoindex, la sous-requte n'hrite pas des
+   variables d'environnement spcifiques  la requte. En outre,  cause
+   des phases de l'API auxquelles mod_setenvif prend
+   part, les directives SetEnvIf ne sont pas values
+   sparment dans la sous-requte.
    
+
+  
+
+  
    Require all
    
+
+    
    Le fournisseur all reproduit la fonctionnalit
+    prcdemment fournie par les directives 'Allow from all' et 'Deny
+    from all'. Il accepte un argument dont les deux valeurs possibles
+    sont : 'granted' ou 'denied'. Les exemples suivants autorisent ou
+    interdisent l'accs  toutes les requtes.
    
+
+    
    Require all granted
    
+
+
+    
    Require all denied
    
+
+
+  
+
+  
    Require method
    
+
+    
    Le fournisseur method permet d'utiliser la mthode
+    HTTP dans le processus d'autorisation. Les mthodes GET et HEAD sont
+    ici considres comme quivalentes. La mthode TRACE n'est pas
+    supporte par ce fournisseur ; utilisez  la place la directive
+    TraceEnable.
    
+
+    
    Dans l'exemple suivant, seules les mthodes GET, HEAD, POST, et
+    OPTIONS sont autorises :
    
+
+    
    Require method GET POST OPTIONS
    
+
+
+    
    Dans l'exemple suivant, les mthodes GET, HEAD, POST, et OPTIONS
+    sont autorises sans authentification, alors que toutes les autres
+    mthodes ncessitent un utilisateur valide :
    
+
+    
    <RequireAny>
+    Require method GET POST OPTIONS
+    Require valid-user
+</RequireAny>
    
+
+
+  
+  
    Require expr
    
+
+  
    Le fournisseur expr permet d'accorder l'autorisation
+  d'accs en fonction d'expressions arbitraires.
    
+
+    
    Require expr %{TIME_HOUR} -ge 9 && %{TIME_HOUR} -le 17
    
+
+
+    
    <RequireAll>
+    Require expr "!(%{QUERY_STRING} =~ /secret/)"
+    Require expr "%{REQUEST_URI} in { '/example.cgi', '/other.cgi' }" 
+</RequireAll>
    
+
+
+    
    Require expr "!(%{QUERY_STRING} =~ /secret/) && %{REQUEST_URI} in { '/example.cgi', '/other.cgi' }"
    
+
+
+    
    La syntaxe de l'expression est dcrite dans la documentation de ap_expr.
    
+
+    
    Normalement, l'expression est value avant l'authentification.
+    Cependant, si l'expression renvoie false et se rfre  la variable
+    %{REMOTE_USER}, le processus d'authentification sera
+    engag et l'expression rvalue.
    
+
+  
+
+
    top
    
+
    
+
    Cration des alias du fournisseur
+d'autorisation
    
+
+    
    Il est possible de crer des fournisseurs d'autorisation tendus
+    dans le fichier de configuration et de leur assigner un nom d'alias.
+    On peut ensuite utiliser ces fournisseurs aliass dans une
+    directive Require de
+    la mme manire qu'on le ferait pour des fournisseurs d'autorisation
+    de base. En plus de la possibilit de crer et d'aliaser un
+    fournisseur tendu, le mme fournisseur d'autorisation tendu peut
+    tre rfrenc par diverses localisations.
+    
    
+
+    
    Exemple
    
+        
    Dans l'exemple suivant, on cre deux alias de fournisseur
+	d'autorisation ldap diffrents bass sur le fournisseur
+	d'autorisation ldap-group. Il est ainsi possible pour un seul
+	rpertoire de vrifier l'appartenance  un groupe dans plusieurs
+	serveurs ldap :
+        
    
+
+        
    <AuthzProviderAlias ldap-group ldap-group-alias1 cn=my-group,o=ctx>
+    AuthLDAPBindDN cn=youruser,o=ctx
+    AuthLDAPBindPassword yourpassword
+    AuthLDAPURL ldap://ldap.host/o=ctx
+</AuthzProviderAlias>
+
+<AuthzProviderAlias ldap-group ldap-group-alias2 cn=my-other-group,o=dev>
+    AuthLDAPBindDN cn=yourotheruser,o=dev
+    AuthLDAPBindPassword yourotherpassword
+    AuthLDAPURL ldap://other.ldap.host/o=dev?cn
+</AuthzProviderAlias>
+
+Alias /secure /webpages/secure
+<Directory /webpages/secure>
+    Require all granted
+
+    AuthBasicProvider file
+
+    AuthType Basic
+    AuthName LDAP_Protected_Place
+
+    #Opration logique implicite : OU inclusif
+    Require ldap-group-alias1
+    Require ldap-group-alias2
+</Directory>
    
+
+    
+
+
    
 
    top
    
 
    Directive AuthMerging
    
 
@@ -438,208 +640,6 @@ pas.
  • Authentification, autorisation et
 contrle d'accs
    • 
-
-
    top
    
-
    
-
    Conteneurs d'autorisation
    
-
-    
    Les directives de conteneur d'autorisation <RequireAll>,
-    <RequireAny> et <RequireNone>
-    peuvent tre combines entre elles et avec la directive Require pour construire une
-    logique d'autorisation complexe.
    
-
-    
    L'exemple ci-dessous illustre la logique d'autorisation suivante.
-    Pour pouvoir accder  la ressource, l'utilisateur doit tre
-    l'utilisateur superadmin, ou appartenir aux deux
-    groupes LDAP admins et Administrateurs et
-    soit appartenir au groupe ventes, soit avoir
-    ventes comme valeur de l'attribut LDAP
-    dept. De plus, pour pouvoir accder  la ressource,
-    l'utilisateur ne doit appartenir ni au groupe temps, ni
-    au groupe LDAP Employs temporaires.
    
-
-    
    <Directory /www/mydocs>
-    <RequireAll>
-        <RequireAny>
-            Require user superadmin
-            <RequireAll>
-            Require group admins
-            Require ldap-group cn=Administrateurs,o=Airius
-                <RequireAny>
-                Require group ventes
-                Require ldap-attribute dept="ventes"
-                </RequireAny>
-            </RequireAll>
-        </RequireAny>
-        <RequireNone>
-            Require group temps
-            Require ldap-group cn=Employs temporaires,o=Airius
-        </RequireNone>
-    </RequireAll>
-</Directory>
    
-
-
    top
    
-
    
-
    Les directives Require
    
-
-  
    Le module mod_authz_core met  disposition des
-  fournisseurs d'autorisation gnriques utilisables avec la directive
-  Require.
    
-
-  
    Require env
    
-
-    
    Le fournisseur env permet de contrler l'accs au
-    serveur en fonction de l'existence d'une variable d'environnement. Lorsque Require
-    env env-variable est spcifi, la requte se voit
-    autoriser l'accs si la variable d'environnement
-    env-variable existe. Le serveur permet de dfinir
-    facilement des variables d'environnement en fonction des
-    caractristiques de la requte du client via les directives fournies
-    par le module mod_setenvif. Cette directive Require
-    env permet donc de contrler l'accs en fonction des
-    valeurs des en-ttes de la requte HTTP tels que
-    User-Agent (type de navigateur), Referer,
-    entre autres.
    
-
-    
    SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in
-<Directory /docroot>
-    Require env let_me_in
-</Directory>
    
-
-
-    
    Avec cet exemple, les navigateurs dont la chane user-agent
-    commence par KnockKnock/2.0 se verront autoriser
-    l'accs, alors que tous les autres seront rejets.
    
-
-    
    Lorsque le serveur cherche un chemin via une sous-requte interne (par exemple la
-   recherche d'un DirectoryIndex), ou lorsqu'il gnre un
-   listing du contenu d'un rpertoire via le module
-   mod_autoindex, la sous-requte n'hrite pas des
-   variables d'environnement spcifiques  la requte. En outre,  cause
-   des phases de l'API auxquelles mod_setenvif prend
-   part, les directives SetEnvIf ne sont pas values
-   sparment dans la sous-requte.
    
-
-  
-
-  
    Require all
    
-
-    
    Le fournisseur all reproduit la fonctionnalit
-    prcdemment fournie par les directives 'Allow from all' et 'Deny
-    from all'. Il accepte un argument dont les deux valeurs possibles
-    sont : 'granted' ou 'denied'. Les exemples suivants autorisent ou
-    interdisent l'accs  toutes les requtes.
    
-
-    
    Require all granted
    
-
-
-    
    Require all denied
    
-
-
-  
-
-  
    Require method
    
-
-    
    Le fournisseur method permet d'utiliser la mthode
-    HTTP dans le processus d'autorisation. Les mthodes GET et HEAD sont
-    ici considres comme quivalentes. La mthode TRACE n'est pas
-    supporte par ce fournisseur ; utilisez  la place la directive
-    TraceEnable.
    
-
-    
    Dans l'exemple suivant, seules les mthodes GET, HEAD, POST, et
-    OPTIONS sont autorises :
    
-
-    
    Require method GET POST OPTIONS
    
-
-
-    
    Dans l'exemple suivant, les mthodes GET, HEAD, POST, et OPTIONS
-    sont autorises sans authentification, alors que toutes les autres
-    mthodes ncessitent un utilisateur valide :
    
-
-    
    <RequireAny>
-    Require method GET POST OPTIONS
-    Require valid-user
-</RequireAny>
    
-
-
-  
-  
    Require expr
    
-
-  
    Le fournisseur expr permet d'accorder l'autorisation
-  d'accs en fonction d'expressions arbitraires.
    
-
-    
    Require expr %{TIME_HOUR} -ge 9 && %{TIME_HOUR} -le 17
    
-
-
-    
    <RequireAll>
-    Require expr "!(%{QUERY_STRING} =~ /secret/)"
-    Require expr "%{REQUEST_URI} in { '/example.cgi', '/other.cgi' }" 
-</RequireAll>
    
-
-
-    
    Require expr "!(%{QUERY_STRING} =~ /secret/) && %{REQUEST_URI} in { '/example.cgi', '/other.cgi' }"
    
-
-
-    
    La syntaxe de l'expression est dcrite dans la documentation de ap_expr.
    
-
-    
    Normalement, l'expression est value avant l'authentification.
-    Cependant, si l'expression renvoie false et se rfre  la variable
-    %{REMOTE_USER}, le processus d'authentification sera
-    engag et l'expression rvalue.
    
-
-  
-
-
    top
    
-
    
-
    Cration des alias du fournisseur
-d'autorisation
    
-
-    
    Il est possible de crer des fournisseurs d'autorisation tendus
-    dans le fichier de configuration et de leur assigner un nom d'alias.
-    On peut ensuite utiliser ces fournisseurs aliass dans une
-    directive Require de
-    la mme manire qu'on le ferait pour des fournisseurs d'autorisation
-    de base. En plus de la possibilit de crer et d'aliaser un
-    fournisseur tendu, le mme fournisseur d'autorisation tendu peut
-    tre rfrenc par diverses localisations.
-    
    
-
-    
    Exemple
    
-        
    Dans l'exemple suivant, on cre deux alias de fournisseur
-	d'autorisation ldap diffrents bass sur le fournisseur
-	d'autorisation ldap-group. Il est ainsi possible pour un seul
-	rpertoire de vrifier l'appartenance  un groupe dans plusieurs
-	serveurs ldap :
-        
    
-
-        
    <AuthzProviderAlias ldap-group ldap-group-alias1 cn=my-group,o=ctx>
-    AuthLDAPBindDN cn=youruser,o=ctx
-    AuthLDAPBindPassword yourpassword
-    AuthLDAPURL ldap://ldap.host/o=ctx
-</AuthzProviderAlias>
-
-<AuthzProviderAlias ldap-group ldap-group-alias2 cn=my-other-group,o=dev>
-    AuthLDAPBindDN cn=yourotheruser,o=dev
-    AuthLDAPBindPassword yourotherpassword
-    AuthLDAPURL ldap://other.ldap.host/o=dev?cn
-</AuthzProviderAlias>
-
-Alias /secure /webpages/secure
-<Directory /webpages/secure>
-    Require all granted
-
-    AuthBasicProvider file
-
-    AuthType Basic
-    AuthName LDAP_Protected_Place
-
-    #Opration logique implicite : OU inclusif
-    Require ldap-group-alias1
-    Require ldap-group-alias2
-</Directory>
    
-
-    
-
 
    
diff --git a/docs/manual/mod/mod_authz_dbd.html.en b/docs/manual/mod/mod_authz_dbd.html.en
index c494f7a0af..157a1fa340 100644
--- a/docs/manual/mod/mod_authz_dbd.html.en
+++ b/docs/manual/mod/mod_authz_dbd.html.en
@@ -71,90 +71,6 @@
 
  • DBDParams
    • 
 
    top
    
-
    AuthzDBDLoginToReferer Directive
    
-
    
 
 
 
 
 
    
-
-
-
-
-
-
-
    Description:Determines whether to redirect the Client to the Referring
-page on successful login or logout if a Referer request
-header is present
    Syntax:AuthzDBDLoginToReferer On|Off
    Default:AuthzDBDLoginToReferer Off
    Context:directory
    Status:Extension
    Module:mod_authz_dbd
    
-    
    In conjunction with Require dbd-login or
-    Require dbd-logout, this provides the option to
-    redirect the client back to the Referring page (the URL in
-    the Referer HTTP request header, if present).
-    When there is no Referer header,
-    AuthzDBDLoginToReferer On will be ignored.
    
-
-
    
-
    top
    
-
    AuthzDBDQuery Directive
    
-
-
-
-
-
-
-
    Description:Specify the SQL Query for the required operation
    Syntax:AuthzDBDQuery query
    Context:directory
    Status:Extension
    Module:mod_authz_dbd
    
-    
    The AuthzDBDQuery specifies an SQL
-    query to run.  The purpose of the query depends on the
-    Require directive in
-    effect.
    
-    
      
-    
    • When used with a Require dbd-group directive,
-    it specifies a query to look up groups for the current user.  This is
-    the standard functionality of other authorization modules such as
-    mod_authz_groupfile and mod_authz_dbm.
-    The first column value of each row returned by the query statement
-    should be a string containing a group name.  Zero, one, or more rows
-    may be returned.
-    
      Require dbd-group
-AuthzDBDQuery "SELECT group FROM groups WHERE user = %s"
      
-
-    
      • 
-    
    • When used with a Require dbd-login or
-    Require dbd-logout directive, it will never deny access,
-    but will instead execute a SQL statement designed to log the user
-    in or out.  The user must already be authenticated with
-    mod_authn_dbd.
-    
      Require dbd-login
-AuthzDBDQuery "UPDATE authn SET login = 'true' WHERE user = %s"
      
-
-    
      • 
-    
    
-    
    In all cases, the user's ID will be passed as a single string
-    parameter when the SQL query is executed.  It may be referenced within
-    the query statement using a %s format specifier.
    
-
-
    
-
    top
    
-
    AuthzDBDRedirectQuery Directive
    
-
-
-
-
-
-
-
    Description:Specify a query to look up a login page for the user
    Syntax:AuthzDBDRedirectQuery query
    Context:directory
    Status:Extension
    Module:mod_authz_dbd
    
-    
    Specifies an optional SQL query to use after successful login
-    (or logout) to redirect the user to a URL, which may be
-    specific to the user.  The user's ID will be passed as a single string
-    parameter when the SQL query is executed.  It may be referenced within
-    the query statement using a %s format specifier.
    
-    
    AuthzDBDRedirectQuery "SELECT userpage FROM userpages WHERE user = %s"
    
-
-    
    The first column value of the first row returned by the query
-    statement should be a string containing a URL to which to redirect
-    the client.  Subsequent rows will be ignored.  If no rows are returned,
-    the client will not be redirected.
    
-    
    Note that AuthzDBDLoginToReferer takes
-    precedence if both are set.
    
-
-
    
-
    top
    
 
    
 
    The Require Directives
    
 
@@ -240,7 +156,7 @@ DBDKeep 8
 DBDMax  20
 DBDExptime 300
 
-<Directory /usr/www/my.site/team-private/>
+<Directory "/usr/www/my.site/team-private/">
   # mod_authn_core and mod_auth_basic configuration
   # for mod_authn_dbd
   AuthType Basic
@@ -262,7 +178,7 @@ DBDExptime 300
   # to /team-private/login.html
   ErrorDocument 401 /login-info.html
 
-  <Files login.html>
+  <Files "login.html">
     # don't require user to already be logged in!
     AuthDBDUserPWQuery "SELECT password FROM authn WHERE user = %s"
 
@@ -275,7 +191,7 @@ DBDExptime 300
     AuthzDBDLoginToReferer On
   </Files>
 
-  <Files logout.html>
+  <Files "logout.html">
     # dbd-logout action executes a statement to log user out
     Require dbd-logout
     AuthzDBDQuery "UPDATE authn SET login = 'false' WHERE user = %s"
@@ -294,6 +210,90 @@ DBDExptime 300
   
    Please read mod_dbd documentation for more information
   about security on this scope.
    
 
    
+
    top
    
+
    AuthzDBDLoginToReferer Directive
    
+
+
+
+
+
+
+
+
    Description:Determines whether to redirect the Client to the Referring
+page on successful login or logout if a Referer request
+header is present
    Syntax:AuthzDBDLoginToReferer On|Off
    Default:AuthzDBDLoginToReferer Off
    Context:directory
    Status:Extension
    Module:mod_authz_dbd
    
+    
    In conjunction with Require dbd-login or
+    Require dbd-logout, this provides the option to
+    redirect the client back to the Referring page (the URL in
+    the Referer HTTP request header, if present).
+    When there is no Referer header,
+    AuthzDBDLoginToReferer On will be ignored.
    
+
+
    
+
    top
    
+
    AuthzDBDQuery Directive
    
+
+
+
+
+
+
+
    Description:Specify the SQL Query for the required operation
    Syntax:AuthzDBDQuery query
    Context:directory
    Status:Extension
    Module:mod_authz_dbd
    
+    
    The AuthzDBDQuery specifies an SQL
+    query to run.  The purpose of the query depends on the
+    Require directive in
+    effect.
    
+    
      
+    
    • When used with a Require dbd-group directive,
+    it specifies a query to look up groups for the current user.  This is
+    the standard functionality of other authorization modules such as
+    mod_authz_groupfile and mod_authz_dbm.
+    The first column value of each row returned by the query statement
+    should be a string containing a group name.  Zero, one, or more rows
+    may be returned.
+    
      Require dbd-group
+AuthzDBDQuery "SELECT group FROM groups WHERE user = %s"
      
+
+    
      • 
+    
    • When used with a Require dbd-login or
+    Require dbd-logout directive, it will never deny access,
+    but will instead execute a SQL statement designed to log the user
+    in or out.  The user must already be authenticated with
+    mod_authn_dbd.
+    
      Require dbd-login
+AuthzDBDQuery "UPDATE authn SET login = 'true' WHERE user = %s"
      
+
+    
      • 
+    
    
+    
    In all cases, the user's ID will be passed as a single string
+    parameter when the SQL query is executed.  It may be referenced within
+    the query statement using a %s format specifier.
    
+
+
    
+
    top
    
+
    AuthzDBDRedirectQuery Directive
    
+
+
+
+
+
+
+
    Description:Specify a query to look up a login page for the user
    Syntax:AuthzDBDRedirectQuery query
    Context:directory
    Status:Extension
    Module:mod_authz_dbd
    
+    
    Specifies an optional SQL query to use after successful login
+    (or logout) to redirect the user to a URL, which may be
+    specific to the user.  The user's ID will be passed as a single string
+    parameter when the SQL query is executed.  It may be referenced within
+    the query statement using a %s format specifier.
    
+    
    AuthzDBDRedirectQuery "SELECT userpage FROM userpages WHERE user = %s"
    
+
+    
    The first column value of the first row returned by the query
+    statement should be a string containing a URL to which to redirect
+    the client.  Subsequent rows will be ignored.  If no rows are returned,
+    the client will not be redirected.
    
+    
    Note that AuthzDBDLoginToReferer takes
+    precedence if both are set.
    
+
+
    
 
 
    
 
    Available Languages:  en  |
diff --git a/docs/manual/mod/mod_authz_dbd.html.fr b/docs/manual/mod/mod_authz_dbd.html.fr
index 2f306d22af..3cb7f82ded 100644
--- a/docs/manual/mod/mod_authz_dbd.html.fr
+++ b/docs/manual/mod/mod_authz_dbd.html.fr
@@ -50,20 +50,20 @@ d'Apache
     pilote de la base de donnes sous-jacente et les paramtres de
     connexion, et grer les connexions  la base de donnes.
    
 
    
-
    Directives
    
-
-
    Sujets
    
+
 
    top
    
-
    Directive AuthzDBDLoginToReferer
    
-
-
-
-
-
-
-
-
    Description:Dfinit si le client doit tre redirig vers la page
-d'origine en cas de connexion ou de dconnexion russie si une en-tte
-de requte Referer est prsente
    Syntaxe:AuthzDBDLoginToReferer On|Off
    Dfaut:AuthzDBDLoginToReferer Off
    Contexte:rpertoire
    Statut:Extension
    Module:mod_authz_dbd
    
-    
    Utilise en conjonction avec Require dbd-login ou
-    Require dbd-logout, cette directive permet de rediriger
-    le client vers la page d'origine (l'URL contenue dans l'en-tte
-    de requte HTTP Referer, s'il est prsent). En
-    l'absence d'en-tte Referer, la dfinition
-    AuthzDBDLoginToReferer On sera ignore.
    
-
-
    
-
    top
    
-
    Directive AuthzDBDQuery
    
-
-
-
-
-
-
-
    Description:Dfinit la requte SQL pour l'opration
-requise
    Syntaxe:AuthzDBDQuery requte
    Contexte:rpertoire
    Statut:Extension
    Module:mod_authz_dbd
    
-    
    La directive AuthzDBDQuery permet de
-    spcifier une requte SQL  excuter. Le but de cette requte dpend
-    de la directive Require en cours de
-    traitement.
    
-    
      
-    
    • Avec la directive Require dbd-group, elle spcifie
-    une requte permettant de rechercher les groupes d'appartenance de
-    l'utilisateur courant. Ceci correspond  la fonctionnalit standard
-    d'autres modules d'autorisation comme
-    mod_authz_groupfile et
-    mod_authz_dbm.
-    La premire colonne de chaque enregistrement renvoy par la requte
-    doit contenir une chane de caractres correspondant  un nom de
-    groupe. La requte peut renvoyer zro, un ou plusieurs
-    enregistrements.
-    
      Require dbd-group
-AuthzDBDQuery "SELECT group FROM groups WHERE user = %s"
      
-
-    
      • 
-    
    • Avec la directive Require dbd-login ou
-    Require dbd-logout, elle ne refusera jamais l'accs,
-    mais au contraire excutera une requte SQL permettant d'enregistrer
-    la connexion ou la dconnexion de l'utilisateur. Ce dernier doit
-    tre dj authentifi avec mod_authn_dbd.
-    
      Require dbd-login
-AuthzDBDQuery "UPDATE authn SET login = 'true' WHERE user = %s"
      
-
-    
      • 
-    
    
-    
    Dans tous les cas, l'identifiant utilisateur sera transmis comme
-    paramtre sous la forme d'une simple chane lorsque la requte SQL
-    sera excute. Il y sera fait rfrence dans la requte en utilisant
-    le spcificateur de format %s.
    
-
-
    
-
    top
    
-
    Directive AuthzDBDRedirectQuery
    
-
-
-
-
-
-
-
    Description:Dfinit une requte pour rechercher une page vers laquelle
-rediriger l'utilisateur aprs une connexion russie
    Syntaxe:AuthzDBDRedirectQuery requte
    Contexte:rpertoire
    Statut:Extension
    Module:mod_authz_dbd
    
-    
    Spcifie une requte SQL optionnelle  utiliser aprs une
-    connexion (ou une dconnexion) russie pour rediriger l'utilisateur
-    vers une URL, qui peut tre spcifique  l'utilisateur.
-    L'identifiant utilisateur sera transmis comme paramtre sous la
-    forme d'une simple chane lorsque la requte SQL sera excute. Il y
-    sera fait rfrence dans la requte en utilisant le spcificateur de
-    format %s.
    
-    
    AuthzDBDRedirectQuery "SELECT userpage FROM userpages WHERE user = %s"
    
-
-    
    La premire colonne du premier enregistrement renvoy par la
-    requte doit contenir une chane de caractres correspondant  une
-    URL vers laquelle rediriger le client. Les enregistrements suivants
-    sont ignors. Si aucun enregistrement n'est renvoy, le client ne
-    sera pas redirig.
    
-    
    Notez que AuthzDBDLoginToReferer l'emporte
-    sur cette directive si les deux sont dfinies.
    
-
-
    
-
    top
    
 
    
 
    Les directives Require
    
 
@@ -316,6 +223,99 @@ DBDExptime 300
   mod_dbd pour plus d'informations  propos de la
   scurit dans ce domaine.
    
 
    
+
    top
    
+
    Directive AuthzDBDLoginToReferer
    
+
+
+
+
+
+
+
+
    Description:Dfinit si le client doit tre redirig vers la page
+d'origine en cas de connexion ou de dconnexion russie si une en-tte
+de requte Referer est prsente
    Syntaxe:AuthzDBDLoginToReferer On|Off
    Dfaut:AuthzDBDLoginToReferer Off
    Contexte:rpertoire
    Statut:Extension
    Module:mod_authz_dbd
    
+    
    Utilise en conjonction avec Require dbd-login ou
+    Require dbd-logout, cette directive permet de rediriger
+    le client vers la page d'origine (l'URL contenue dans l'en-tte
+    de requte HTTP Referer, s'il est prsent). En
+    l'absence d'en-tte Referer, la dfinition
+    AuthzDBDLoginToReferer On sera ignore.
    
+
+
    
+
    top
    
+
    Directive AuthzDBDQuery
    
+
+
+
+
+
+
+
    Description:Dfinit la requte SQL pour l'opration
+requise
    Syntaxe:AuthzDBDQuery requte
    Contexte:rpertoire
    Statut:Extension
    Module:mod_authz_dbd
    
+    
    La directive AuthzDBDQuery permet de
+    spcifier une requte SQL  excuter. Le but de cette requte dpend
+    de la directive Require en cours de
+    traitement.
    
+    
      
+    
    • Avec la directive Require dbd-group, elle spcifie
+    une requte permettant de rechercher les groupes d'appartenance de
+    l'utilisateur courant. Ceci correspond  la fonctionnalit standard
+    d'autres modules d'autorisation comme
+    mod_authz_groupfile et
+    mod_authz_dbm.
+    La premire colonne de chaque enregistrement renvoy par la requte
+    doit contenir une chane de caractres correspondant  un nom de
+    groupe. La requte peut renvoyer zro, un ou plusieurs
+    enregistrements.
+    
      Require dbd-group
+AuthzDBDQuery "SELECT group FROM groups WHERE user = %s"
      
+
+    
      • 
+    
    • Avec la directive Require dbd-login ou
+    Require dbd-logout, elle ne refusera jamais l'accs,
+    mais au contraire excutera une requte SQL permettant d'enregistrer
+    la connexion ou la dconnexion de l'utilisateur. Ce dernier doit
+    tre dj authentifi avec mod_authn_dbd.
+    
      Require dbd-login
+AuthzDBDQuery "UPDATE authn SET login = 'true' WHERE user = %s"
      
+
+    
      • 
+    
    
+    
    Dans tous les cas, l'identifiant utilisateur sera transmis comme
+    paramtre sous la forme d'une simple chane lorsque la requte SQL
+    sera excute. Il y sera fait rfrence dans la requte en utilisant
+    le spcificateur de format %s.
    
+
+
    
+
    top
    
+
    Directive AuthzDBDRedirectQuery
    
+
+
+
+
+
+
+
    Description:Dfinit une requte pour rechercher une page vers laquelle
+rediriger l'utilisateur aprs une connexion russie
    Syntaxe:AuthzDBDRedirectQuery requte
    Contexte:rpertoire
    Statut:Extension
    Module:mod_authz_dbd
    
+    
    Spcifie une requte SQL optionnelle  utiliser aprs une
+    connexion (ou une dconnexion) russie pour rediriger l'utilisateur
+    vers une URL, qui peut tre spcifique  l'utilisateur.
+    L'identifiant utilisateur sera transmis comme paramtre sous la
+    forme d'une simple chane lorsque la requte SQL sera excute. Il y
+    sera fait rfrence dans la requte en utilisant le spcificateur de
+    format %s.
    
+    
    AuthzDBDRedirectQuery "SELECT userpage FROM userpages WHERE user = %s"
    
+
+    
    La premire colonne du premier enregistrement renvoy par la
+    requte doit contenir une chane de caractres correspondant  une
+    URL vers laquelle rediriger le client. Les enregistrements suivants
+    sont ignors. Si aucun enregistrement n'est renvoy, le client ne
+    sera pas redirig.
    
+    
    Notez que AuthzDBDLoginToReferer l'emporte
+    sur cette directive si les deux sont dfinies.
    
+
+
    
 
    
 
    
 
    Langues Disponibles:  en  |
diff --git a/docs/manual/mod/mod_authz_dbd.xml b/docs/manual/mod/mod_authz_dbd.xml
index 0f548ea496..0292c86257 100644
--- a/docs/manual/mod/mod_authz_dbd.xml
+++ b/docs/manual/mod/mod_authz_dbd.xml
@@ -140,7 +140,7 @@ DBDKeep 8
 DBDMax  20
 DBDExptime 300
 
-<Directory /usr/www/my.site/team-private/>
+<Directory "/usr/www/my.site/team-private/">
   # mod_authn_core and mod_auth_basic configuration
   # for mod_authn_dbd
   AuthType Basic
@@ -162,7 +162,7 @@ DBDExptime 300
   # to /team-private/login.html
   ErrorDocument 401 /login-info.html
 
-  <Files login.html>
+  <Files "login.html">
     # don't require user to already be logged in!
     AuthDBDUserPWQuery "SELECT password FROM authn WHERE user = %s"
 
@@ -175,7 +175,7 @@ DBDExptime 300
     AuthzDBDLoginToReferer On
   </Files>
 
-  <Files logout.html>
+  <Files "logout.html">
     # dbd-logout action executes a statement to log user out
     Require dbd-logout
     AuthzDBDQuery "UPDATE authn SET login = 'false' WHERE user = %s"
diff --git a/docs/manual/mod/mod_authz_dbm.html.en b/docs/manual/mod/mod_authz_dbm.html.en
index 3121966606..b3735797f2 100644
--- a/docs/manual/mod/mod_authz_dbm.html.en
+++ b/docs/manual/mod/mod_authz_dbm.html.en
@@ -53,6 +53,55 @@
 
  • Require
    • 
 
    
 
    top
    
+
    
+
    The Require Directives
    
+
+    
    Apache's Require
+    directives are used during the authorization phase to ensure that
+    a user is allowed to access a resource.  mod_authz_dbm extends the
+    authorization types with dbm-group.
    
+
+    
    Since v2.4.8, expressions are supported
+    within the DBM require directives.
    
+
+
    Require dbm-group
    
+
+    
    This directive specifies group membership that is required for the
+    user to gain access.
    
+
+    
    Require dbm-group admin
    
+
+
+
+
+
    Require dbm-file-group
    
+
+    
    When this directive is specified, the user must be a member of the group
+    assigned to the file being accessed.
    
+
+    
    Require dbm-file-group
    
+
+
+
+
+
    top
    
+
    
+
    Example usage
    
+
+
    Note that using mod_authz_dbm requires you to require dbm-group
+instead of group:
+
    
+
    <Directory "/foo/bar">
+  AuthType Basic
+  AuthName "Secure Area"
+  AuthBasicProvider dbm
+  AuthDBMUserFile "site/data/users"
+  AuthDBMGroupFile "site/data/users"
+  Require dbm-group admin
+</Directory>
    
+
+
    
+
    top
    
 
    AuthDBMGroupFile Directive
    
 
    It is crucial that whatever program you use to create your group
     files is configured to use the same type of database.
    
 
-
-
    top
    
-
    
-
    The Require Directives
    
-
-    
    Apache's Require
-    directives are used during the authorization phase to ensure that
-    a user is allowed to access a resource.  mod_authz_dbm extends the
-    authorization types with dbm-group.
    
-
-    
    Since v2.4.8, expressions are supported
-    within the DBM require directives.
    
-
-
    Require dbm-group
    
-
-    
    This directive specifies group membership that is required for the
-    user to gain access.
    
-
-    
    Require dbm-group admin
    
-
-
-
-
-
    Require dbm-file-group
    
-
-    
    When this directive is specified, the user must be a member of the group
-    assigned to the file being accessed.
    
-
-    
    Require dbm-file-group
    
-
-
-
-
-
    top
    
-
    
-
    Example usage
    
-
-
    Note that using mod_authz_dbm requires you to require dbm-group
-instead of group:
-
    
-
    <Directory "/foo/bar">
-  AuthType Basic
-  AuthName "Secure Area"
-  AuthBasicProvider dbm
-  AuthDBMUserFile "site/data/users"
-  AuthDBMGroupFile "site/data/users"
-  Require dbm-group admin
-</Directory>
    
-
 
    
diff --git a/docs/manual/mod/mod_authz_dbm.html.fr b/docs/manual/mod/mod_authz_dbm.html.fr
index 001b01cdb6..4f9a243c10 100644
--- a/docs/manual/mod/mod_authz_dbm.html.fr
+++ b/docs/manual/mod/mod_authz_dbm.html.fr
@@ -42,20 +42,70 @@
     mod_authz_groupfile fournit une fonctionnalit
     similaire.
    
 
    
-
    Directives
    
+
 
    top
    
+
    
+
    The Require Directives
    
+
+    
    Les directives Require d'Apache permettent,
+    au cours de la phase d'autorisation, de s'assurer qu'un utilisateur
+    est bien autoris  accder  une ressource.  mod_authz_dbm ajoute
+    les types d'autorisation dbm-group et dbm-file-group.
    
+
+    
    A partir de la version 2.4.8, les directives require DBM
+    supportent les expressions.
    
+
+
    Require dbm-group
    
+
+    
    Cette directive permet de spcifier  quel groupe un utilisateur
+    doit appartenir pour obtenir l'autorisation d'accs.
    
+
+    
    Require dbm-group admin
    
+
+
+
+
+
    Require dbm-file-group
    
+
+    
    Lorsque cette directive est dfinie, l'utilisateur doit
+    appartenir au groupe du fichier pour pouvoir y accder.
    
+
+    
    Require dbm-file-group
    
+
+
+
+
+
    top
    
+
    
+
    Exemple d'utilisation
    
+
+
    Notez que si vous utilisez mod_authz_dbm, le mot-cl pour les
+groupes d'authentification qui tait auparavant group est
+maintenant dbm-group :
+
    
+
    <Directory "/foo/bar">
+  AuthType Basic
+  AuthName "Secure Area"
+  AuthBasicProvider dbm
+  AuthDBMUserFile site/data/users
+  AuthDBMGroupFile site/data/users
+  Require dbm-group admin
+</Directory>
    
+
+
    
+
    top
    
 
    Directive AuthDBMGroupFile
    
 
    
 
    Description:Sets the name of the database file containing the list
@@ -130,55 +179,6 @@ store list of user groups
    
     
 
 
    
     fichier de groupes, il est impratif que celui-ci soit configur
     pour utiliser le mme type de base de donnes.
    
 
-
-
    top
    
-
    
-
    The Require Directives
    
-
-    
    Les directives Require d'Apache permettent,
-    au cours de la phase d'autorisation, de s'assurer qu'un utilisateur
-    est bien autoris  accder  une ressource.  mod_authz_dbm ajoute
-    les types d'autorisation dbm-group et dbm-file-group.
    
-
-    
    A partir de la version 2.4.8, les directives require DBM
-    supportent les expressions.
    
-
-
    Require dbm-group
    
-
-    
    Cette directive permet de spcifier  quel groupe un utilisateur
-    doit appartenir pour obtenir l'autorisation d'accs.
    
-
-    
    Require dbm-group admin
    
-
-
-
-
-
    Require dbm-file-group
    
-
-    
    Lorsque cette directive est dfinie, l'utilisateur doit
-    appartenir au groupe du fichier pour pouvoir y accder.
    
-
-    
    Require dbm-file-group
    
-
-
-
-
-
    top
    
-
    
-
    Exemple d'utilisation
    
-
-
    Notez que si vous utilisez mod_authz_dbm, le mot-cl pour les
-groupes d'authentification qui tait auparavant group est
-maintenant dbm-group :
-
    
-
    <Directory "/foo/bar">
-  AuthType Basic
-  AuthName "Secure Area"
-  AuthBasicProvider dbm
-  AuthDBMUserFile site/data/users
-  AuthDBMGroupFile site/data/users
-  Require dbm-group admin
-</Directory>
    
-
 
    
diff --git a/docs/manual/mod/mod_authz_dbm.html.ko.euc-kr b/docs/manual/mod/mod_authz_dbm.html.ko.euc-kr
index 43511705c6..6cf0d2201b 100644
--- a/docs/manual/mod/mod_authz_dbm.html.ko.euc-kr
+++ b/docs/manual/mod/mod_authz_dbm.html.ko.euc-kr
@@ -51,6 +51,7 @@
 
  • Require
    • 
 
  • Satisfy
    • 
 
    
+
 
    top
    AuthDBMGroupFile þ
    
 
    
 
    Description:Dfinit le nom du fichier de base de donnes qui liste
@@ -137,56 +187,6 @@ la liste des groupes d'utilisateurs
    
 
 
 
    
@@ -121,7 +122,6 @@
     ϵ ؾ Ѵ.
    
-
 
    
 
     :  en  |
diff --git a/docs/manual/mod/mod_authz_groupfile.html.en b/docs/manual/mod/mod_authz_groupfile.html.en
index 883304b283..81b141abc2 100644
--- a/docs/manual/mod/mod_authz_groupfile.html.en
+++ b/docs/manual/mod/mod_authz_groupfile.html.en
@@ -52,40 +52,6 @@
 
  • Require
    • 
 
    top
    
-
    AuthGroupFile Directive
    
-
    
 
 
 
 
    
-
-
-
-
-
-
-
    Description:Sets the name of a text file containing the list
-of user groups for authorization
    Syntax:AuthGroupFile file-path
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Base
    Module:mod_authz_groupfile
    
-    
    The AuthGroupFile directive sets the
-    name of a textual file containing the list of user groups for user
-    authorization. File-path is the path to the group
-    file. If it is not absolute, it is treated as relative to the ServerRoot.
    
-
-    
    Each line of the group file contains a groupname followed by a
-    colon, followed by the member usernames separated by spaces.
    
-
-    
    Example:
    
-      mygroup: bob joe anne
-    
    
-
-    
    Note that searching large text files is very
-    inefficient; AuthDBMGroupFile provides a much better performance.
    
-
-    
    Security
    
-      
    Make sure that the AuthGroupFile is
-      stored outside the document tree of the web-server; do not
-      put it in the directory that it protects. Otherwise, clients may
-      be able to download the AuthGroupFile.
    
-    
    
-
-
    
-
    top
    
 
    
 
    The Require Directives
    
 
@@ -118,6 +84,40 @@ of user groups for authorization
 
 
 
+
    
+
    top
    
+
    AuthGroupFile Directive
    
+
+
+
+
+
+
+
+
    Description:Sets the name of a text file containing the list
+of user groups for authorization
    Syntax:AuthGroupFile file-path
    Context:directory, .htaccess
    Override:AuthConfig
    Status:Base
    Module:mod_authz_groupfile
    
+    
    The AuthGroupFile directive sets the
+    name of a textual file containing the list of user groups for user
+    authorization. File-path is the path to the group
+    file. If it is not absolute, it is treated as relative to the ServerRoot.
    
+
+    
    Each line of the group file contains a groupname followed by a
+    colon, followed by the member usernames separated by spaces.
    
+
+    
    Example:
    
+      mygroup: bob joe anne
+    
    
+
+    
    Note that searching large text files is very
+    inefficient; AuthDBMGroupFile provides a much better performance.
    
+
+    
    Security
    
+      
    Make sure that the AuthGroupFile is
+      stored outside the document tree of the web-server; do not
+      put it in the directory that it protects. Otherwise, clients may
+      be able to download the AuthGroupFile.
    
+    
    
+
 
    
 
 
    
diff --git a/docs/manual/mod/mod_authz_groupfile.html.fr b/docs/manual/mod/mod_authz_groupfile.html.fr
index f05ebbb4ba..fc90ef6e2a 100644
--- a/docs/manual/mod/mod_authz_groupfile.html.fr
+++ b/docs/manual/mod/mod_authz_groupfile.html.fr
@@ -41,18 +41,52 @@ certaines zones du site web aux utilisateurs authentifi
 fonction de leur appartenance  un groupe spcifi. Le module
 mod_authz_dbm fournit une fonctionnalit similaire.
    
 
    
-
    Directives
    
+
    Sujets
    
+
    Directives
    
 
-
    Sujets
    
-
    Voir aussi
    
+
    Voir aussi
    
 
    
 
    top
    
+
    
+
    The Require Directives
    
+
+    
    Les directives Require d'Apache permettent,
+    au cours de la phase d'autorisation, de s'assurer qu'un utilisateur
+    est bien autoris  accder  une ressource. mod_authz_groupfile ajoute
+    les types d'autorisation group et file-group.
+    
    
+
+    
    A partir de la version 2.4.8, les directives require groupfile
+    supportent les expressions.
    
+
+
    Require group
    
+
+    
    Cette directive permet de spcifier  quel groupe un utilisateur
+    doit appartenir pour obtenir l'autorisation d'accs.
    
+
+    
    Require group admin
    
+
+
+
+
+
    Require file-group
    
+
+    
    Lorsque cette directive est dfinie, l'utilisateur doit
+    appartenir au groupe du fichier pour pouvoir y accder.
    
+
+    
    Require file-group
    
+
+
+
+
+
    
+
    top
    
 
    Directive AuthGroupFile
    
 
       multiples" (MultiViews) d'un contenu ngoci.
    
-
    Directives
    
-
    Ce module ne fournit aucune directive.
    
-
    Sujets
    
+
    Sujets
    
 
    Voir aussi
    
+
    Directives
    
+
    Ce module ne fournit aucune directive.
    
+
    Voir aussi
    
 
    
diff --git a/docs/manual/mod/mod_authz_owner.html.ja.utf8 b/docs/manual/mod/mod_authz_owner.html.ja.utf8
index 1af36918a9..37a5a81217 100644
--- a/docs/manual/mod/mod_authz_owner.html.ja.utf8
+++ b/docs/manual/mod/mod_authz_owner.html.ja.utf8
@@ -79,12 +79,12 @@
       決して承認しません。
    
     
    
-
    ディレクティブ
    
-
    このモジュールにディレクティブはありません。
    
-
    トピック
    
+
    トピック
    
 
    参照
    
+
    ディレクティブ
    
+
    このモジュールにディレクティブはありません。
    
+
    参照
    
 
    
diff --git a/docs/manual/mod/mod_authz_owner.html.ko.euc-kr b/docs/manual/mod/mod_authz_owner.html.ko.euc-kr
index b5b9d4c549..9ad039b31e 100644
--- a/docs/manual/mod/mod_authz_owner.html.ko.euc-kr
+++ b/docs/manual/mod/mod_authz_owner.html.ko.euc-kr
@@ -73,12 +73,12 @@
       "MultiViews" ڿ Ѻο ʴ´.
    
     
    
-
    þ
    
-
     ⿡ þ ϴ.
    
-
    
+
    
 
    
+
    þ
    
+
     ⿡ þ ϴ.
    
+
    
 
      
 
    • Require
      • 
 
    • Satisfy
      • 
diff --git a/docs/manual/mod/mod_authz_user.html.fr b/docs/manual/mod/mod_authz_user.html.fr
index ca1c355356..9145abf9a7 100644
--- a/docs/manual/mod/mod_authz_user.html.fr
+++ b/docs/manual/mod/mod_authz_user.html.fr
@@ -43,12 +43,12 @@
     Require valid-user pour accorder l'accs  tous les
     utilisateurs qui ont t authentifis avec succs.
      
 
    
-
    Directives
    
-
    Ce module ne fournit aucune directive.
    
-
    Sujets
    
+
    Sujets
    
 
    Voir aussi
    
+
    Directives
    
+
    Ce module ne fournit aucune directive.
    
+
    Voir aussi
    
 
    
diff --git a/docs/manual/mod/mod_autoindex.html.en b/docs/manual/mod/mod_autoindex.html.en
index f97dfbfd58..4e649e2165 100644
--- a/docs/manual/mod/mod_autoindex.html.en
+++ b/docs/manual/mod/mod_autoindex.html.en
@@ -104,6 +104,108 @@
 
 
    
 
    top
    
+
    
+
    Autoindex Request Query Arguments
    
+    
+
+    
    Various query string arguments are available to give the client
+    some control over the ordering of the directory listing, as well as
+    what files are listed. If you do not wish to give the client this
+    control, the IndexOptions
+    IgnoreClient option disables that functionality.
    
+
+    
    The column sorting headers themselves are self-referencing
+    hyperlinks that add the sort query options shown below. Any
+    option below may be added to any request for the directory
+    resource.
    
+
+    
      
+      
    • C=N sorts the directory by file name
      • 
+
+      
    • C=M sorts the directory by last-modified
+      date, then file name
      • 
+
+      
    • C=S sorts the directory by size, then file
+      name
      • 
+
+      
    • C=D sorts the directory by description, then
+      file name
      • 
+
+      
    • O=A sorts the listing in Ascending
+      Order
      • 
+
+      
    • O=D sorts the listing in Descending
+      Order
      • 
+
+      
    • F=0 formats the listing as a simple list
+      (not FancyIndexed)
      • 
+
+      
    • F=1 formats the listing as a FancyIndexed
+      list
      • 
+
+      
    • F=2 formats the listing as an
+      HTMLTable FancyIndexed list
      • 
+
+      
    • V=0 disables version sorting
      • 
+
+      
    • V=1 enables version sorting
      • 
+
+      
    • P=pattern lists only files matching
+      the given pattern
      • 
+    
    
+
+    
    Note that the 'P'attern query argument is tested
+    after the usual IndexIgnore directives are processed,
+    and all file names are still subjected to the same criteria as
+    any other autoindex listing. The Query Arguments parser in
+    mod_autoindex will stop abruptly when an unrecognized
+    option is encountered. The Query Arguments must be well formed,
+    according to the table above.
    
+
+    
    The simple example below, which can be clipped and saved in
+    a header.html file, illustrates these query options. Note that
+    the unknown "X" argument, for the submit button, is listed last
+    to assure the arguments are all parsed before mod_autoindex
+    encounters the X=Go input.
    
+
+    
    
+      <form action="" method="get">
    
+      
+        Show me a <select name="F">
    
+        
+          <option value="0"> Plain list</option>
    
+          <option value="1" selected="selected"> Fancy list</option>
    
+          <option value="2"> Table list</option>
    
+            
+        </select>
    
+        Sorted by <select name="C">
    
+        
+          <option value="N" selected="selected"> Name</option>
    
+          <option value="M"> Date Modified</option>
    
+          <option value="S"> Size</option>
    
+          <option value="D"> Description</option>
    
+            
+        </select>
    
+        <select name="O">
    
+        
+          <option value="A" selected="selected"> Ascending</option>
    
+          <option value="D"> Descending</option>
    
+            
+        </select>
    
+        <select name="V">
    
+        
+          <option value="0" selected="selected"> in Normal order</option>
    
+          <option value="1"> in Version order</option>
    
+            
+        </select>
    
+        Matching <input type="text" name="P" value="*" />
    
+        <input type="submit" name="X" value="Go" />
    
+          
+      </form>
+    
    
+
+
    
+
    top
    
 
    AddAlt Directive
    
 
    
 
    Description:Dfinit le nom d'un fichier texte contenant la liste des
@@ -90,40 +124,6 @@ s
 clients pourraient le tlcharger.
    
     
 
-
-
    top
    
-
    
-
    The Require Directives
    
-
-    
    Les directives Require d'Apache permettent,
-    au cours de la phase d'autorisation, de s'assurer qu'un utilisateur
-    est bien autoris  accder  une ressource. mod_authz_groupfile ajoute
-    les types d'autorisation group et file-group.
-    
    
-
-    
    A partir de la version 2.4.8, les directives require groupfile
-    supportent les expressions.
    
-
-
    Require group
    
-
-    
    Cette directive permet de spcifier  quel groupe un utilisateur
-    doit appartenir pour obtenir l'autorisation d'accs.
    
-
-    
    Require group admin
    
-
-
-
-
-
    Require file-group
    
-
-    
    Lorsque cette directive est dfinie, l'utilisateur doit
-    appartenir au groupe du fichier pour pouvoir y accder.
    
-
-    
    Require file-group
    
-
-
-
-
 
    
 
 
    
diff --git a/docs/manual/mod/mod_authz_groupfile.html.ja.utf8 b/docs/manual/mod/mod_authz_groupfile.html.ja.utf8
index 39d9989a66..a58b83c2f9 100644
--- a/docs/manual/mod/mod_authz_groupfile.html.ja.utf8
+++ b/docs/manual/mod/mod_authz_groupfile.html.ja.utf8
@@ -53,6 +53,7 @@
 
    
+
 
    top
    
 
    AuthGroupFile ディレクティブ
    
 
@@ -94,7 +95,6 @@
     
-
 
    
 
    翻訳済み言語:  en  |
diff --git a/docs/manual/mod/mod_authz_groupfile.html.ko.euc-kr b/docs/manual/mod/mod_authz_groupfile.html.ko.euc-kr
index 65d7dfbd8e..eeb65c8fc5 100644
--- a/docs/manual/mod/mod_authz_groupfile.html.ko.euc-kr
+++ b/docs/manual/mod/mod_authz_groupfile.html.ko.euc-kr
@@ -51,6 +51,7 @@
 
  • Require
    • 
 
  • Satisfy
    • 
 
    
+
 
    top
    AuthGroupFile þ
    
 
    
 
 
 
 
    
@@ -85,7 +86,6 @@
     
-
 
    
 
     :  en  |
diff --git a/docs/manual/mod/mod_authz_host.html.fr b/docs/manual/mod/mod_authz_host.html.fr
index 9de473cdf6..afdbc8db28 100644
--- a/docs/manual/mod/mod_authz_host.html.fr
+++ b/docs/manual/mod/mod_authz_host.html.fr
@@ -52,12 +52,12 @@ d'Apache
    
 
 
 
    
     mthodes sans protection, en plaant les directives dans une section
     <Limit>.
    
 
    
-
    Directives
    
-
    Ce module ne fournit aucune directive.
    
-
    Sujets
    
+
    Sujets
    
 
    Voir aussi
    
+
    Directives
    
+
    Ce module ne fournit aucune directive.
    
+
    Voir aussi
    
 
      
 
    • Authentification, autorisation et
 contrle d'accs
      • 
diff --git a/docs/manual/mod/mod_authz_owner.html.fr b/docs/manual/mod/mod_authz_owner.html.fr
index 745d712180..2cb41e8af0 100644
--- a/docs/manual/mod/mod_authz_owner.html.fr
+++ b/docs/manual/mod/mod_authz_owner.html.fr
@@ -81,12 +81,12 @@ fichiers
    
     
 
 
 
    
     any files ignored by IndexIgnore otherwise
     inherited from other configuration sections. 
    
 
-    
    <Directory /var/www>
+    
    <Directory "/var/www">
     IndexIgnore *.bak .??* *~ *# HEADER* README* RCS CVS *,v *,t
 </Directory>
-<Directory /var/www/backups>
+<Directory "/var/www/backups">
     IndexIgnoreReset ON
     IndexIgnore .??* *# HEADER* README* RCS CVS *,v *,t
 </Directory>
    
@@ -800,7 +902,7 @@ indexing
      
  • Multiple IndexOptions directives for a
      single directory are now merged together. The result of:
 
-     
    <Directory /foo>
+     
    <Directory "/foo">
     IndexOptions HTMLTable
     IndexOptions SuppressColumnsorting
 </Directory>
    
@@ -938,108 +1040,6 @@ ReadmeName /include/FOOTER.html
    
     
    See also HeaderName, where this behavior is described in greater
     detail.
    
 
-
-
    top
    
-
    
-
    Autoindex Request Query Arguments
    
-    
-
-    
    Various query string arguments are available to give the client
-    some control over the ordering of the directory listing, as well as
-    what files are listed. If you do not wish to give the client this
-    control, the IndexOptions
-    IgnoreClient option disables that functionality.
    
-
-    
    The column sorting headers themselves are self-referencing
-    hyperlinks that add the sort query options shown below. Any
-    option below may be added to any request for the directory
-    resource.
    
-
-    
      
-      
    • C=N sorts the directory by file name
      • 
-
-      
    • C=M sorts the directory by last-modified
-      date, then file name
      • 
-
-      
    • C=S sorts the directory by size, then file
-      name
      • 
-
-      
    • C=D sorts the directory by description, then
-      file name
      • 
-
-      
    • O=A sorts the listing in Ascending
-      Order
      • 
-
-      
    • O=D sorts the listing in Descending
-      Order
      • 
-
-      
    • F=0 formats the listing as a simple list
-      (not FancyIndexed)
      • 
-
-      
    • F=1 formats the listing as a FancyIndexed
-      list
      • 
-
-      
    • F=2 formats the listing as an
-      HTMLTable FancyIndexed list
      • 
-
-      
    • V=0 disables version sorting
      • 
-
-      
    • V=1 enables version sorting
      • 
-
-      
    • P=pattern lists only files matching
-      the given pattern
      • 
-    
    
-
-    
    Note that the 'P'attern query argument is tested
-    after the usual IndexIgnore directives are processed,
-    and all file names are still subjected to the same criteria as
-    any other autoindex listing. The Query Arguments parser in
-    mod_autoindex will stop abruptly when an unrecognized
-    option is encountered. The Query Arguments must be well formed,
-    according to the table above.
    
-
-    
    The simple example below, which can be clipped and saved in
-    a header.html file, illustrates these query options. Note that
-    the unknown "X" argument, for the submit button, is listed last
-    to assure the arguments are all parsed before mod_autoindex
-    encounters the X=Go input.
    
-
-    
    
-      <form action="" method="get">
    
-      
-        Show me a <select name="F">
    
-        
-          <option value="0"> Plain list</option>
    
-          <option value="1" selected="selected"> Fancy list</option>
    
-          <option value="2"> Table list</option>
    
-            
-        </select>
    
-        Sorted by <select name="C">
    
-        
-          <option value="N" selected="selected"> Name</option>
    
-          <option value="M"> Date Modified</option>
    
-          <option value="S"> Size</option>
    
-          <option value="D"> Description</option>
    
-            
-        </select>
    
-        <select name="O">
    
-        
-          <option value="A" selected="selected"> Ascending</option>
    
-          <option value="D"> Descending</option>
    
-            
-        </select>
    
-        <select name="V">
    
-        
-          <option value="0" selected="selected"> in Normal order</option>
    
-          <option value="1"> in Version order</option>
    
-            
-        </select>
    
-        Matching <input type="text" name="P" value="*" />
    
-        <input type="submit" name="X" value="Go" />
    
-          
-      </form>
-    
    
-
 
    
 
 
    
diff --git a/docs/manual/mod/mod_autoindex.html.fr b/docs/manual/mod/mod_autoindex.html.fr
index 03008e29d0..000277a41d 100644
--- a/docs/manual/mod/mod_autoindex.html.fr
+++ b/docs/manual/mod/mod_autoindex.html.fr
@@ -30,6 +30,8 @@
  ko  |
  tr 
    
 
    
+
    Cette traduction peut tre prime. Vrifiez la version
+            anglaise pour les changements rcents.
    
 
    • 
 
    Description:Alternate text to display for a file, instead of an
@@ -463,10 +565,10 @@ a directory
    
@@ -77,7 +79,10 @@ shell Win32 dir
     affich avant un fichier de 1011 octets (en ordre croissant), mme
     si la taille affiche des deux fichiers est "1K".
    
-
+
    top
    
+
    
+
    Arguments de la requte d'autoindexation
    
+    
+
+    
    La chane de paramtres de la requte peut contenir de nombreux
+    arguments permettant dans une certaine mesure au client de contrler
+    l'ordre de l'index du rpertoire, ainsi que la liste des fichiers 
+    afficher. Si vous souhaitez dsactiver cette fonctionnalit,
+    utilisez l'option IndexOptions
+    IgnoreClient.
    
+
+    
    Les en-ttes de tri des colonnes eux-mmes sont des hyper-liens
+    auto-rfrant qui ajoutent les options de tri  la requte numres
+    ci-dessous qui peuvent tre ajoutes  toute requte concernant la
+    ressource rpertoire.
    
+
+    
      
+      
    • C=N trie l'affichage en fonction du nom de
+      fichier
      • 
+
+      
    • C=M trie l'affichage en fonction de la date de
+      dernire modification, puis du nom de fichier
      • 
+
+      
    • C=S trie l'affichage en fonction de la taille,
+      puis du nom de fichier
      • 
+
+      
    • C=D trie l'affichage en fonction
+      de la description, puis du nom de fichier
      • 
+
+      
    • O=A trie l'affichage selon l'ordre croissant
      • 
+
+      
    • O=D trie l'affichage selon
+      l'ordre dcroissant
      • 
+
+      
    • F=0 affiche le listing sous la forme d'une simple
+      liste (sans FancyIndex)
      • 
+
+      
    • F=1 affiche le listing avec en-ttes de colonnes
+      sous forme de liens hyper-textes (FancyIndexed)
      • 
+
+      
    • F=2 affiche le listing sous
+      forme de table HTML avec en-ttes de colonnes contenant des liens
+      hyper-textes (FancyIndexed)
      • 
+
+      
    • V=0 dsactive le tri en fonction de la
+      version
      • 
+
+      
    • V=1 active le tri en fonction de
+      la version
      • 
+
+      
    • P=modle n'affiche que les fichiers
+      correspondant au modle spcifi
      • 
+    
    
+
+    
    Notez que l'argument 'P' (pour Pattern) n'est test
+    qu'aprs que les directives habituelles IndexIgnore ont t traites,
+    et que tous les noms de fichiers sont encore assujettis aux mmes
+    critres que pour tout autre listing auto-index. L'interprteur
+    d'arguments de requte de mod_autoindex s'arrte
+    immdiatement s'il rencontre une option non reconnue. Les arguments
+    de requte doivent tre bien forms, selon la table ci-dessus.
    
+
+    
    Les options de requtes sont illustres par l'exemple ci-dessous,
+    qui peut tre copi et coll dans un fichier header.html. Notez que
+    l'argument inconnu "X", pour le bouton submit, est introduit en
+    dernier afin de s'assurer que tous les arguments ont t
+    interprts avant que mod_autoindex ne rencontre l'entre X=Go.
    
+
+    
    
+      <form action="" method="get">
    
+      
+        Montre moi une <select name="F">
    
+        
+          <option value="0"> liste simple</option>
    
+          <option value="1" selected="selected"> liste avec
+	  en-ttes</option>
    
+          <option value="2"> liste avec en-tte sous forme de
+	  table</option>
    
+            
+        </select>
    
+        trie par <select name="C">
    
+        
+          <option value="N" selected="selected"> nom</option>
    
+          <option value="M"> date de modification</option>
    
+          <option value="S"> taille</option>
    
+          <option value="D"> description</option>
    
+            
+        </select>
    
+        <select name="O">
    
+        
+          <option value="A" selected="selected"> croissant</option>
    
+          <option value="D"> dcroissant</option>
    
+            
+        </select>
    
+        <select name="V">
    
+        
+          <option value="0" selected="selected"> dans l'ordre
+	  normal</option>
    
+          <option value="1"> en fonction de la version</option>
    
+            
+        </select>
    
+        correspondant  <input type="text" name="P" value="*" />
    
+        <input type="submit" name="X" value="Go" />
    
+          
+      </form>
+    
    
+
+
    top
    Directive AddAlt
    
 
    Description:Gnre automatiquement des index de rpertoires d'une
 manire similaire  la commande Unix ls, ou  la commande
 shell Win32 dir
    
 
 
 
    
@@ -988,115 +1099,6 @@ ReadmeName /include/FOOTER.html
    Voir aussi la directive HeaderName, o cette fonctionnalit est dcrite plus en
     dtails.
    
 
-
-
    top
    
-
    
-
    Arguments de la requte d'autoindexation
    
-    
-
-    
    La chane de paramtres de la requte peut contenir de nombreux
-    arguments permettant dans une certaine mesure au client de contrler
-    l'ordre de l'index du rpertoire, ainsi que la liste des fichiers 
-    afficher. Si vous souhaitez dsactiver cette fonctionnalit,
-    utilisez l'option IndexOptions
-    IgnoreClient.
    
-
-    
    Les en-ttes de tri des colonnes eux-mmes sont des hyper-liens
-    auto-rfrant qui ajoutent les options de tri  la requte numres
-    ci-dessous qui peuvent tre ajoutes  toute requte concernant la
-    ressource rpertoire.
    
-
-    
      
-      
    • C=N trie l'affichage en fonction du nom de
-      fichier
      • 
-
-      
    • C=M trie l'affichage en fonction de la date de
-      dernire modification, puis du nom de fichier
      • 
-
-      
    • C=S trie l'affichage en fonction de la taille,
-      puis du nom de fichier
      • 
-
-      
    • C=D trie l'affichage en fonction
-      de la description, puis du nom de fichier
      • 
-
-      
    • O=A trie l'affichage selon l'ordre croissant
      • 
-
-      
    • O=D trie l'affichage selon
-      l'ordre dcroissant
      • 
-
-      
    • F=0 affiche le listing sous la forme d'une simple
-      liste (sans FancyIndex)
      • 
-
-      
    • F=1 affiche le listing avec en-ttes de colonnes
-      sous forme de liens hyper-textes (FancyIndexed)
      • 
-
-      
    • F=2 affiche le listing sous
-      forme de table HTML avec en-ttes de colonnes contenant des liens
-      hyper-textes (FancyIndexed)
      • 
-
-      
    • V=0 dsactive le tri en fonction de la
-      version
      • 
-
-      
    • V=1 active le tri en fonction de
-      la version
      • 
-
-      
    • P=modle n'affiche que les fichiers
-      correspondant au modle spcifi
      • 
-    
    
-
-    
    Notez que l'argument 'P' (pour Pattern) n'est test
-    qu'aprs que les directives habituelles IndexIgnore ont t traites,
-    et que tous les noms de fichiers sont encore assujettis aux mmes
-    critres que pour tout autre listing auto-index. L'interprteur
-    d'arguments de requte de mod_autoindex s'arrte
-    immdiatement s'il rencontre une option non reconnue. Les arguments
-    de requte doivent tre bien forms, selon la table ci-dessus.
    
-
-    
    Les options de requtes sont illustres par l'exemple ci-dessous,
-    qui peut tre copi et coll dans un fichier header.html. Notez que
-    l'argument inconnu "X", pour le bouton submit, est introduit en
-    dernier afin de s'assurer que tous les arguments ont t
-    interprts avant que mod_autoindex ne rencontre l'entre X=Go.
    
-
-    
    
-      <form action="" method="get">
    
-      
-        Montre moi une <select name="F">
    
-        
-          <option value="0"> liste simple</option>
    
-          <option value="1" selected="selected"> liste avec
-	  en-ttes</option>
    
-          <option value="2"> liste avec en-tte sous forme de
-	  table</option>
    
-            
-        </select>
    
-        trie par <select name="C">
    
-        
-          <option value="N" selected="selected"> nom</option>
    
-          <option value="M"> date de modification</option>
    
-          <option value="S"> taille</option>
    
-          <option value="D"> description</option>
    
-            
-        </select>
    
-        <select name="O">
    
-        
-          <option value="A" selected="selected"> croissant</option>
    
-          <option value="D"> dcroissant</option>
    
-            
-        </select>
    
-        <select name="V">
    
-        
-          <option value="0" selected="selected"> dans l'ordre
-	  normal</option>
    
-          <option value="1"> en fonction de la version</option>
    
-            
-        </select>
    
-        correspondant  <input type="text" name="P" value="*" />
    
-        <input type="submit" name="X" value="Go" />
    
-          
-      </form>
-    
    
-
 
    
diff --git a/docs/manual/mod/mod_autoindex.html.ja.utf8 b/docs/manual/mod/mod_autoindex.html.ja.utf8
index b5d266829c..52f802b7ab 100644
--- a/docs/manual/mod/mod_autoindex.html.ja.utf8
+++ b/docs/manual/mod/mod_autoindex.html.ja.utf8
@@ -89,7 +89,10 @@
     1010 バイトのファイルは必ず 1011
     バイトのファイルよりも前 (昇順の場合) に表示されます。
    
 
    
-
    ディレクティブ
    
+
+
    
+
    top
    
+
    
+
    Autoindex リクエストクエリー引数
    
+    
+
+    
    Apache 2.0.23 で、
+    コラムソートのためにクエリー引数を再編成して、
+    新しいクエリーオプションのグループを導入しました。
+    出力に対するクライアントのすべての制御を効率的に抹消
+    できるように、
+    IndexOptions
+    IgnoreClient が導入されました。
    
+
+    
    コラムソートのヘッダそれ自体が、
+    下記のソートクエリーオプションを付加する
+    自分自身を参照するリンクです。
+    下記のオプションのどれでも、
+    ディレクトリリソースへのリクエストに加えることができます。
    
+
+    
      
+      
    • C=N は、ファイル名でソートします。
      • 
+
+      
    • C=M は、更新日時、
+      ディレクトリ、ファイル名の順でソートします。
      • 
+
+      
    • C=S は、サイズ、
+      ディレクトリ、ファイル名の順でソートします。
      • 
+
+      
    • C=D は、説明、
+      ディレクトリ、ファイル名の順でソートします。
      • 
+
+      
    • O=A は、昇順で表をソートします。
      • 
+
+      
    • O=D は、降順で表をソートします。
      • 
+
+      
    • F=0 は、単純な表の書式にします。
+      (FancyIndex ではありません。)
      • 
+
+      
    • F=1 は、FancyIndex 
+      表示の表の書式にします。
      • 
+
+      
    • F=2 は、表を HTML 
+      のテーブルを使った FancyIndex の書式にします。
      • 
+
+      
    • V=0 
+      は、バージョンによるソートを無効にします。
      • 
+
+      
    • V=1 
+      は、バージョンによるソートを有効にします。
      • 
+
+      
    • P=pattern 
+      は、与えられた pattern
+      に適合したファイルのみを表示します。
      • 
+    
    
+
+    
    "P (パターンの P)" クエリー引数は、
+    通常の IndexIgnore
+    ディレクティブが処理された後に検査され、
+    ファイル名全てが、他の autoindex
+    リスト処理と同様の判定基準下に置かれ続ける
+    ことに注意してください。
+    mod_autoindex のクエリー引数パーサ (解析) は、
+    認識不能なオプションにぶつかると即座に停止します。
+    クエリー引数は上の表に従って
+    正しい形式になっていなければなりません。
    
+
+    
    下の単純な例は、これらのクエリーオプションを
+    表します。これをそのまま切り取って HEADER.html 
+    ファイルに保存することもできます。
+    mod_autoindex が X=Go 入力にぶつかる前に
+    引数が全て解釈されるように、
+    未知の引数 "X" はリストの最後に置かれています。
    
+
+    
    
+      <form action="" method="get">
    
+      
+        Show me a <select name="F">
    
+        
+          <option value="0"> Plain list</option>
    
+          <option value="1" selected="selected"> Fancy list</option>
    
+          <option value="2"> Table list</option>
    
+            
+        </select>
    
+        Sorted by <select name="C">
    
+        
+          <option value="N" selected="selected"> Name</option>
    
+          <option value="M"> Date Modified</option>
    
+          <option value="S"> Size</option>
    
+          <option value="D"> Description</option>
    
+            
+        </select>
    
+        <select name="O">
    
+        
+          <option value="A" selected="selected"> Ascending</option>
    
+          <option value="D"> Descending</option>
    
+            
+        </select>
    
+        <select name="V">
    
+        
+          <option value="0" selected="selected"> in Normal order</option>
    
+          <option value="1"> in Version order</option>
    
+            
+        </select>
    
+        Matching <input type="text" name="P" value="*" />
    
+        <input type="submit" name="X" value="Go" />
    
+          
+      </form>
+    
    
+
+
    top
    AddAlt ディレクティブ
    
 
    
     
 
 
 
 
    
@@ -932,116 +1042,6 @@ Name|Date|Size|Description
    より詳細にまでこの挙動について記述している HeaderName
     もご覧下さい。
    
 
-
-
    top
    
-
    
-
    Autoindex リクエストクエリー引数
    
-    
-
-    
    Apache 2.0.23 で、
-    コラムソートのためにクエリー引数を再編成して、
-    新しいクエリーオプションのグループを導入しました。
-    出力に対するクライアントのすべての制御を効率的に抹消
-    できるように、
-    IndexOptions
-    IgnoreClient が導入されました。
    
-
-    
    コラムソートのヘッダそれ自体が、
-    下記のソートクエリーオプションを付加する
-    自分自身を参照するリンクです。
-    下記のオプションのどれでも、
-    ディレクトリリソースへのリクエストに加えることができます。
    
-
-    
      
-      
    • C=N は、ファイル名でソートします。
      • 
-
-      
    • C=M は、更新日時、
-      ディレクトリ、ファイル名の順でソートします。
      • 
-
-      
    • C=S は、サイズ、
-      ディレクトリ、ファイル名の順でソートします。
      • 
-
-      
    • C=D は、説明、
-      ディレクトリ、ファイル名の順でソートします。
      • 
-
-      
    • O=A は、昇順で表をソートします。
      • 
-
-      
    • O=D は、降順で表をソートします。
      • 
-
-      
    • F=0 は、単純な表の書式にします。
-      (FancyIndex ではありません。)
      • 
-
-      
    • F=1 は、FancyIndex 
-      表示の表の書式にします。
      • 
-
-      
    • F=2 は、表を HTML 
-      のテーブルを使った FancyIndex の書式にします。
      • 
-
-      
    • V=0 
-      は、バージョンによるソートを無効にします。
      • 
-
-      
    • V=1 
-      は、バージョンによるソートを有効にします。
      • 
-
-      
    • P=pattern 
-      は、与えられた pattern
-      に適合したファイルのみを表示します。
      • 
-    
    
-
-    
    "P (パターンの P)" クエリー引数は、
-    通常の IndexIgnore
-    ディレクティブが処理された後に検査され、
-    ファイル名全てが、他の autoindex
-    リスト処理と同様の判定基準下に置かれ続ける
-    ことに注意してください。
-    mod_autoindex のクエリー引数パーサ (解析) は、
-    認識不能なオプションにぶつかると即座に停止します。
-    クエリー引数は上の表に従って
-    正しい形式になっていなければなりません。
    
-
-    
    下の単純な例は、これらのクエリーオプションを
-    表します。これをそのまま切り取って HEADER.html 
-    ファイルに保存することもできます。
-    mod_autoindex が X=Go 入力にぶつかる前に
-    引数が全て解釈されるように、
-    未知の引数 "X" はリストの最後に置かれています。
    
-
-    
    
-      <form action="" method="get">
    
-      
-        Show me a <select name="F">
    
-        
-          <option value="0"> Plain list</option>
    
-          <option value="1" selected="selected"> Fancy list</option>
    
-          <option value="2"> Table list</option>
    
-            
-        </select>
    
-        Sorted by <select name="C">
    
-        
-          <option value="N" selected="selected"> Name</option>
    
-          <option value="M"> Date Modified</option>
    
-          <option value="S"> Size</option>
    
-          <option value="D"> Description</option>
    
-            
-        </select>
    
-        <select name="O">
    
-        
-          <option value="A" selected="selected"> Ascending</option>
    
-          <option value="D"> Descending</option>
    
-            
-        </select>
    
-        <select name="V">
    
-        
-          <option value="0" selected="selected"> in Normal order</option>
    
-          <option value="1"> in Version order</option>
    
-            
-        </select>
    
-        Matching <input type="text" name="P" value="*" />
    
-        <input type="submit" name="X" value="Go" />
    
-          
-      </form>
-    
    
-
 
    
diff --git a/docs/manual/mod/mod_autoindex.html.ko.euc-kr b/docs/manual/mod/mod_autoindex.html.ko.euc-kr
index 052bec6450..218a2e4d7d 100644
--- a/docs/manual/mod/mod_autoindex.html.ko.euc-kr
+++ b/docs/manual/mod/mod_autoindex.html.ko.euc-kr
@@ -73,7 +73,10 @@
     Ʈ  Ѵ "1K" ̴ ׻ 1010 Ʈ 
     տ ´.
    
 
    
-
+
    top
    
+
    
+
    Autoindex û ƱԸƮ
    
+    
+
+    
    ġ 2.0.23   û ƱԸƮ ϰ,
+    ο ɼǵ ߰ߴ.  Ŭ̾Ʈ  
+      IndexOptions
+    IgnoreClient ɼ ߰Ǿ.
    
+
+    
     ̸ Ʒ   û ɼ  ڱ
+    ũ. Ʒ ɼ 丮 ڿ   û
+      ִ.
    
+
+    
      
+      
    • C=N ϸ ̴
      • 
+
+      
    • C=M ֱ  , ׸ ϸ ̴
      • 
+
+      
    • C=S ũ , ׸ ϸ ̴
      • 
+
+      
    • C=D  , ׸ ϸ
+      ̴
      • 
+
+      
    • O=A   Ѵ
      • 
+
+      
    • O=D   Ѵ
      • 
+
+      
    • F=0 (FancyIndexed ƴ)   ̴
      • 
+
+      
    • F=1 FancyIndexed  ̴
      • 
+
+      
    • F=2 HTMLTable FancyIndexed 
+      ̴
      • 
+
+      
    • V=0    ʴ´
      • 
+
+      
    • V=1   Ѵ
      • 
+
+      
    • P=pattern ־ pattern
+      شϴ ϸ  
      • 
+    
    
+
+    
    'P'attern ƱԸƮ Ϲ IndexIgnore þ ó Ŀ
+    ˻ϱ⶧,  ٸ autoindex   ϶.
+    mod_autoindex û ƱԸƮ о϶
+       ɼ ߰ϸ  ̻ ʴ´. û ƱԸƮ
+     ǥ   Ѵ.
    
+
+    
    header.html Ͽ   ִ Ʒ  
+     ɼǵ Ѵ. submit     "X" ƱԸƮ
+    mod_autoindex X=Go   ƱԸƮ о
+    Ȯϱ  ߴ.
    
+
+    
    
+      <form action="" method="get">
    
+      
+        Show me a <select name="F">
    
+        
+          <option value="0"> Plain list</option>
    
+          <option value="1" selected="selected"> Fancy list</option>
    
+          <option value="2"> Table list</option>
    
+            
+        </select>
    
+        Sorted by <select name="C">
    
+        
+          <option value="N" selected="selected"> Name</option>
    
+          <option value="M"> Date Modified</option>
    
+          <option value="S"> Size</option>
    
+          <option value="D"> Description</option>
    
+            
+        </select>
    
+        <select name="O">
    
+        
+          <option value="A" selected="selected"> Ascending</option>
    
+          <option value="D"> Descending</option>
    
+            
+        </select>
    
+        <select name="V">
    
+        
+          <option value="0" selected="selected"> in Normal order</option>
    
+          <option value="1"> in Version order</option>
    
+            
+        </select>
    
+        Matching <input type="text" name="P" value="*" />
    
+        <input type="submit" name="X" value="Go" />
    
+          
+      </form>
+    
    
+
+
    top
    AddAlt þ
    
 
    
     
 
 
 
 
    
@@ -763,97 +854,6 @@ Name|Date|Size|Description
      ڼ  HeaderName ϶.
    
 
-
-
    top
    
-
    
-
    Autoindex û ƱԸƮ
    
-    
-
-    
    ġ 2.0.23   û ƱԸƮ ϰ,
-    ο ɼǵ ߰ߴ.  Ŭ̾Ʈ  
-      IndexOptions
-    IgnoreClient ɼ ߰Ǿ.
    
-
-    
     ̸ Ʒ   û ɼ  ڱ
-    ũ. Ʒ ɼ 丮 ڿ   û
-      ִ.
    
-
-    
      
-      
    • C=N ϸ ̴
      • 
-
-      
    • C=M ֱ  , ׸ ϸ ̴
      • 
-
-      
    • C=S ũ , ׸ ϸ ̴
      • 
-
-      
    • C=D  , ׸ ϸ
-      ̴
      • 
-
-      
    • O=A   Ѵ
      • 
-
-      
    • O=D   Ѵ
      • 
-
-      
    • F=0 (FancyIndexed ƴ)   ̴
      • 
-
-      
    • F=1 FancyIndexed  ̴
      • 
-
-      
    • F=2 HTMLTable FancyIndexed 
-      ̴
      • 
-
-      
    • V=0    ʴ´
      • 
-
-      
    • V=1   Ѵ
      • 
-
-      
    • P=pattern ־ pattern
-      شϴ ϸ  
      • 
-    
    
-
-    
    'P'attern ƱԸƮ Ϲ IndexIgnore þ ó Ŀ
-    ˻ϱ⶧,  ٸ autoindex   ϶.
-    mod_autoindex û ƱԸƮ о϶
-       ɼ ߰ϸ  ̻ ʴ´. û ƱԸƮ
-     ǥ   Ѵ.
    
-
-    
    header.html Ͽ   ִ Ʒ  
-     ɼǵ Ѵ. submit     "X" ƱԸƮ
-    mod_autoindex X=Go   ƱԸƮ о
-    Ȯϱ  ߴ.
    
-
-    
    
-      <form action="" method="get">
    
-      
-        Show me a <select name="F">
    
-        
-          <option value="0"> Plain list</option>
    
-          <option value="1" selected="selected"> Fancy list</option>
    
-          <option value="2"> Table list</option>
    
-            
-        </select>
    
-        Sorted by <select name="C">
    
-        
-          <option value="N" selected="selected"> Name</option>
    
-          <option value="M"> Date Modified</option>
    
-          <option value="S"> Size</option>
    
-          <option value="D"> Description</option>
    
-            
-        </select>
    
-        <select name="O">
    
-        
-          <option value="A" selected="selected"> Ascending</option>
    
-          <option value="D"> Descending</option>
    
-            
-        </select>
    
-        <select name="V">
    
-        
-          <option value="0" selected="selected"> in Normal order</option>
    
-          <option value="1"> in Version order</option>
    
-            
-        </select>
    
-        Matching <input type="text" name="P" value="*" />
    
-        <input type="submit" name="X" value="Go" />
    
-          
-      </form>
-    
    
-
 
    
diff --git a/docs/manual/mod/mod_autoindex.html.tr.utf8 b/docs/manual/mod/mod_autoindex.html.tr.utf8
index cdc4875038..09f85d3cc2 100644
--- a/docs/manual/mod/mod_autoindex.html.tr.utf8
+++ b/docs/manual/mod/mod_autoindex.html.tr.utf8
@@ -73,7 +73,10 @@ yaptığı gibi dizin içeriğini listeler.
       olanı küçükten büyüğe sıralamada 1011 baytlıktan önce
       gösterilecektir.
    
 
    
-
    Yönergeler
    
+
    Konular
    
+
    Yönergeler
    
 
-
    Konular
    
-
    
+
    
+
    top
    
+
    
+
    Sütun Sıralamada Sorgu Seçenekleri
    
+    
+
+    
    İstemciye, dizin içeriğini listelerken neleri hangi sırada
+      listeleyeceğini belirleyebilmesi için içerik üzerinde biraz denetim
+      sağlayabileceği çeşitli sorgu dizgesi bileşenleri sağlanmıştır.
+      Çıktı üzerinde kullanıcı denetimini tamamen ortadan kaldırmak için
+      IndexOptions yönergesinin
+      IgnoreClient
+      seçeneği kullanılabilir.
    
+
+    
    Sütun sıralama başlıklarının her biri hedefi kendisi olan birer hiper
+      bağ olup aşağıda sıralanan sorgu seçeneklerini kullanırlar. Bu
+      seçeneklerin her biri her dizin içerik listesi isteğine eklenebilir.
    
+
+    
      
+      
    • C=N dizini dosya adına göre sıralar
      • 
+
+      
    • C=M dizini son değişiklik zamanına ve ardından dosya
+        ismine göre sıralar.
      • 
+
+      
    • C=S dizini boyuta ve ardından dosya adına göre
+        sıralar
      • 
+
+      
    • C=D dizini açıklamaya ve ardından
+        dosya adına göre sıralar.
      • 
+
+      
    • O=A artan sıralama uygulanır.
      • 
+
+      
    • O=D  azalan sıralama uygulanır.
      • 
+
+      
    • F=0 listeleme basit listeleme biçiminde yapılır
+        (FancyIndexing seçeneği ile etkinleştirilen biçimde
+        değil)
      • 
+
+      
    • F=1 listeleme FancyIndexing seçeneği ile
+        etkinleştirilen biçimde yapılır
      • 
+
+      
    • F=2 listeleme FancyIndexing ve
+        HTMLTable seçeneği
+        ile etkinleştirilen biçimde yapılır.
      • 
+
+      
    • V=0 sürüme göre sıralama iptal edilir.
      • 
+
+      
    • V=1 sürüme göre sıralama etkin
+        kılınır.
      • 
+
+      
    • P=kalıp sadece belirtilen
+        kalıp ile eşleşen dosyalar istelenir.
      • 
+    
    
+
+    
    P=kalıp sorgu seçeneğinin normalde IndexIgnore yönergesi işleme
+      sokulduktan sonra değerlendirildiğine ve dosya isimlerinin diğer
+      kendiliğinden içerik listeleme koşullarının konusu olmaya devam ettiğine
+      dikkat ediniz. mod_autoindex modülündeki Sorgu
+      Seçenekleri çözümleyicisi tanımadığı bir seçeneğe rastlar rastlamaz
+      işlemi durdurur. Sorgu Seçenekleri yukarıda belirtilene uygun olarak iyi
+      biçimli olmak zorundadır.
    
+
+    
    Aşağıdaki basit örnekte sorgu seçeneklerinin kullanımı gösterilmiştir.
+      Son satırda bulunan "submit" düğmesindeki tanınmayan "X" girdisine
+      dikkat ediniz. "X=Göster" girdisi tüm seçenekler işlendikten sonra
+      mod_autoindex tarafından son argüman olarak ele
+      alınacak ve çözümleme işlemi o noktada duracaktır.
    
+
+    
    <form action="" method="get">
+  <input type="text" name="P" value="*" /> ile eşleşen
+  <select name="C">
+    <option value="N" selected="selected">isme</option>
+    <option value="M"> değişiklik tarihine</option>
+    <option value="S"> boyuta</option>
+    <option value="D"> açıklamaya</option>
+  </select> göre
+  <select name="O">
+    <option value="A" selected="selected"> artan</option>
+    <option value="D"> azalan</option>
+  </select>
+  <select name="V">
+    <option value="0" selected="selected">normal</option>
+    <option value="1"> sürümlü</option>
+  </select> sıralamayla bir
+  <select name="F">
+    <option value="0"> basit liste</option>
+    <option value="1" selected="selected"> süslü liste</option>
+    <option value="2"> tablolu liste</option>
+  </select>
+  <input type="submit" name="X" value="Göster" />
+</form>
    
+
+
    top
    AddAlt Yönergesi
    
 
    
 
     
 
 
 
 
    
@@ -944,98 +1036,6 @@ belirler.
    Ayrıca bu davranışın daha ayrıntılı ele alındığı HeaderName yönergesine de
       bakınız.
    
 
-
-
    top
    
-
    
-
    Sütun Sıralamada Sorgu Seçenekleri
    
-    
-
-    
    İstemciye, dizin içeriğini listelerken neleri hangi sırada
-      listeleyeceğini belirleyebilmesi için içerik üzerinde biraz denetim
-      sağlayabileceği çeşitli sorgu dizgesi bileşenleri sağlanmıştır.
-      Çıktı üzerinde kullanıcı denetimini tamamen ortadan kaldırmak için
-      IndexOptions yönergesinin
-      IgnoreClient
-      seçeneği kullanılabilir.
    
-
-    
    Sütun sıralama başlıklarının her biri hedefi kendisi olan birer hiper
-      bağ olup aşağıda sıralanan sorgu seçeneklerini kullanırlar. Bu
-      seçeneklerin her biri her dizin içerik listesi isteğine eklenebilir.
    
-
-    
      
-      
    • C=N dizini dosya adına göre sıralar
      • 
-
-      
    • C=M dizini son değişiklik zamanına ve ardından dosya
-        ismine göre sıralar.
      • 
-
-      
    • C=S dizini boyuta ve ardından dosya adına göre
-        sıralar
      • 
-
-      
    • C=D dizini açıklamaya ve ardından
-        dosya adına göre sıralar.
      • 
-
-      
    • O=A artan sıralama uygulanır.
      • 
-
-      
    • O=D  azalan sıralama uygulanır.
      • 
-
-      
    • F=0 listeleme basit listeleme biçiminde yapılır
-        (FancyIndexing seçeneği ile etkinleştirilen biçimde
-        değil)
      • 
-
-      
    • F=1 listeleme FancyIndexing seçeneği ile
-        etkinleştirilen biçimde yapılır
      • 
-
-      
    • F=2 listeleme FancyIndexing ve
-        HTMLTable seçeneği
-        ile etkinleştirilen biçimde yapılır.
      • 
-
-      
    • V=0 sürüme göre sıralama iptal edilir.
      • 
-
-      
    • V=1 sürüme göre sıralama etkin
-        kılınır.
      • 
-
-      
    • P=kalıp sadece belirtilen
-        kalıp ile eşleşen dosyalar istelenir.
      • 
-    
    
-
-    
    P=kalıp sorgu seçeneğinin normalde IndexIgnore yönergesi işleme
-      sokulduktan sonra değerlendirildiğine ve dosya isimlerinin diğer
-      kendiliğinden içerik listeleme koşullarının konusu olmaya devam ettiğine
-      dikkat ediniz. mod_autoindex modülündeki Sorgu
-      Seçenekleri çözümleyicisi tanımadığı bir seçeneğe rastlar rastlamaz
-      işlemi durdurur. Sorgu Seçenekleri yukarıda belirtilene uygun olarak iyi
-      biçimli olmak zorundadır.
    
-
-    
    Aşağıdaki basit örnekte sorgu seçeneklerinin kullanımı gösterilmiştir.
-      Son satırda bulunan "submit" düğmesindeki tanınmayan "X" girdisine
-      dikkat ediniz. "X=Göster" girdisi tüm seçenekler işlendikten sonra
-      mod_autoindex tarafından son argüman olarak ele
-      alınacak ve çözümleme işlemi o noktada duracaktır.
    
-
-    
    <form action="" method="get">
-  <input type="text" name="P" value="*" /> ile eşleşen
-  <select name="C">
-    <option value="N" selected="selected">isme</option>
-    <option value="M"> değişiklik tarihine</option>
-    <option value="S"> boyuta</option>
-    <option value="D"> açıklamaya</option>
-  </select> göre
-  <select name="O">
-    <option value="A" selected="selected"> artan</option>
-    <option value="D"> azalan</option>
-  </select>
-  <select name="V">
-    <option value="0" selected="selected">normal</option>
-    <option value="1"> sürümlü</option>
-  </select> sıralamayla bir
-  <select name="F">
-    <option value="0"> basit liste</option>
-    <option value="1" selected="selected"> süslü liste</option>
-    <option value="2"> tablolu liste</option>
-  </select>
-  <input type="submit" name="X" value="Göster" />
-</form>
    
-
 
    
diff --git a/docs/manual/mod/mod_autoindex.xml b/docs/manual/mod/mod_autoindex.xml
index 503a08f518..9898bc8722 100644
--- a/docs/manual/mod/mod_autoindex.xml
+++ b/docs/manual/mod/mod_autoindex.xml
@@ -563,10 +563,10 @@ a directory
     inherited from other configuration sections. 
    
 
     
-<Directory /var/www>
+<Directory "/var/www">
     IndexIgnore *.bak .??* *~ *# HEADER* README* RCS CVS *,v *,t
 </Directory>
-<Directory /var/www/backups>
+<Directory "/var/www/backups">
     IndexIgnoreReset ON
     IndexIgnore .??* *# HEADER* README* RCS CVS *,v *,t
 </Directory>
@@ -955,7 +955,7 @@ indexing
      single directory are now merged together. The result of:
 
      
-<Directory /foo>
+<Directory "/foo">
     IndexOptions HTMLTable
     IndexOptions SuppressColumnsorting
 </Directory>
diff --git a/docs/manual/mod/mod_autoindex.xml.fr b/docs/manual/mod/mod_autoindex.xml.fr
index 432b783fe8..9b12837a85 100644
--- a/docs/manual/mod/mod_autoindex.xml.fr
+++ b/docs/manual/mod/mod_autoindex.xml.fr
@@ -1,7 +1,7 @@
 
 
 
-
+
 
 
 
diff --git a/docs/manual/mod/mod_autoindex.xml.ja b/docs/manual/mod/mod_autoindex.xml.ja
index 255cdec477..e0ac8ff3b5 100644
--- a/docs/manual/mod/mod_autoindex.xml.ja
+++ b/docs/manual/mod/mod_autoindex.xml.ja
@@ -1,7 +1,7 @@
 
 
 
-
+
 
 
+
 
 
+