httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n.@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod mod_auth_digest.html.en mod_auth_digest.xml
Date Thu, 12 Dec 2002 00:04:01 GMT
nd          2002/12/11 16:04:01

  Modified:    docs/manual/mod mod_auth_digest.html.en mod_auth_digest.xml
  Log:
  small markup issues
  
  Revision  Changes    Path
  1.17      +7 -8      httpd-2.0/docs/manual/mod/mod_auth_digest.html.en
  
  Index: mod_auth_digest.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_auth_digest.html.en,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- mod_auth_digest.html.en	11 Dec 2002 20:50:34 -0000	1.16
  +++ mod_auth_digest.html.en	12 Dec 2002 00:04:01 -0000	1.17
  @@ -126,19 +126,18 @@
   </table>
       <p>The <code class="directive">AuthDigestDomain</code> 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.</p>
  +    space (<em>i.e.</em> use the same realm and username/password info).
  +    The specified URIs are prefixes, <em>i.e.</em> the client will assume
  +    that all URIs "below" these are also protected by the same
  +    username/password. The URIs may be either absolute URIs (<em>i.e.</em>
  +    inluding a scheme, host, port, etc) or relative URIs.</p>
   
       <p>This directive <em>should</em> 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 <em>every request</em> 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.</p>
  +    also have a detrimental effect on performance if <code class="directive"><a
href="#authdigestnccheck">AuthDigestNcCheck</a></code> is on.</p>
   
       <p>The URIs specified can also point to different servers, in
       which case clients (which understand this) will then share
  @@ -281,7 +280,7 @@
       <div class="example"><p><code>
         AuthDigestShmemSize 1048576<br />
         AuthDigestShmemSize 1024K<br />
  -      AuthDigestShmemSize 1M<br />
  +      AuthDigestShmemSize 1M
       </code></p></div>
   
   </div>
  
  
  
  1.8       +8 -8      httpd-2.0/docs/manual/mod/mod_auth_digest.xml
  
  Index: mod_auth_digest.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_auth_digest.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- mod_auth_digest.xml	9 Dec 2002 22:19:13 -0000	1.7
  +++ mod_auth_digest.xml	12 Dec 2002 00:04:01 -0000	1.8
  @@ -231,19 +231,19 @@
   <usage>
       <p>The <directive>AuthDigestDomain</directive> 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.</p>
  +    space (<em>i.e.</em> use the same realm and username/password info).
  +    The specified URIs are prefixes, <em>i.e.</em> the client will assume
  +    that all URIs "below" these are also protected by the same
  +    username/password. The URIs may be either absolute URIs (<em>i.e.</em>
  +    inluding a scheme, host, port, etc) or relative URIs.</p>
   
       <p>This directive <em>should</em> 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 <em>every request</em> 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.</p>
  +    also have a detrimental effect on performance if <directive
  +    module="mod_auth_digest">AuthDigestNcCheck</directive> is on.</p>
   
       <p>The URIs specified can also point to different servers, in
       which case clients (which understand this) will then share
  @@ -279,7 +279,7 @@
       <example>
         AuthDigestShmemSize 1048576<br />
         AuthDigestShmemSize 1024K<br />
  -      AuthDigestShmemSize 1M<br />
  +      AuthDigestShmemSize 1M
       </example>
   </usage>
   </directivesynopsis>
  
  
  

Mime
View raw message