From 9cc70cc559f6c984cc5ea746e2eaaf94d9456dee Mon Sep 17 00:00:00 2001 From: Andre Malo Date: Thu, 12 Dec 2002 00:04:01 +0000 Subject: [PATCH] small markup issues git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@97882 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_auth_digest.html.en | 15 +++++++-------- docs/manual/mod/mod_auth_digest.xml | 16 ++++++++-------- 2 files changed, 15 insertions(+), 16 deletions(-) diff --git a/docs/manual/mod/mod_auth_digest.html.en b/docs/manual/mod/mod_auth_digest.html.en index 396aabd52d..5ecc263348 100644 --- a/docs/manual/mod/mod_auth_digest.html.en +++ b/docs/manual/mod/mod_auth_digest.html.en @@ -126,19 +126,18 @@ authentication

The AuthDigestDomain directive allows you to specify one or more URIs which are in the same protection - space (i.e. use the same realm and username/password info). The - specified URIs are prefixes, i.e. the client will assume that all - URIs "below" these are also protected by the same - username/password. The URIs may be either absolute URIs - (i.e. inluding a scheme, host, port, etc) or relative URIs.

+ space (i.e. use the same realm and username/password info). + The specified URIs are prefixes, i.e. the client will assume + that all URIs "below" these are also protected by the same + username/password. The URIs may be either absolute URIs (i.e. + inluding a scheme, host, port, etc) or relative URIs.

This directive should always be specified and contain at least the (set of) root URI(s) for this space. Omitting to do so will cause the client to send the Authorization header for every request sent to this server. Apart from increasing the size of the request, it may - also have a detrimental effect on performance if - "AuthDigestNcCheck" is on.

+ also have a detrimental effect on performance if AuthDigestNcCheck is on.

The URIs specified can also point to different servers, in which case clients (which understand this) will then share @@ -281,7 +280,7 @@ of clients

AuthDigestShmemSize 1048576
AuthDigestShmemSize 1024K
- AuthDigestShmemSize 1M
+ AuthDigestShmemSize 1M

diff --git a/docs/manual/mod/mod_auth_digest.xml b/docs/manual/mod/mod_auth_digest.xml index 4709d94b3c..0f25d9d953 100644 --- a/docs/manual/mod/mod_auth_digest.xml +++ b/docs/manual/mod/mod_auth_digest.xml @@ -231,19 +231,19 @@ authentication

The AuthDigestDomain directive allows you to specify one or more URIs which are in the same protection - space (i.e. use the same realm and username/password info). The - specified URIs are prefixes, i.e. the client will assume that all - URIs "below" these are also protected by the same - username/password. The URIs may be either absolute URIs - (i.e. inluding a scheme, host, port, etc) or relative URIs.

+ space (i.e. use the same realm and username/password info). + The specified URIs are prefixes, i.e. the client will assume + that all URIs "below" these are also protected by the same + username/password. The URIs may be either absolute URIs (i.e. + inluding a scheme, host, port, etc) or relative URIs.

This directive should always be specified and contain at least the (set of) root URI(s) for this space. Omitting to do so will cause the client to send the Authorization header for every request sent to this server. Apart from increasing the size of the request, it may - also have a detrimental effect on performance if - "AuthDigestNcCheck" is on.

+ also have a detrimental effect on performance if AuthDigestNcCheck is on.

The URIs specified can also point to different servers, in which case clients (which understand this) will then share @@ -279,7 +279,7 @@ of clients AuthDigestShmemSize 1048576
AuthDigestShmemSize 1024K
- AuthDigestShmemSize 1M
+ AuthDigestShmemSize 1M
-- 2.40.0