httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: httpd-2.0/docs/manual/mod mod_auth_digest.xml
Date Sun, 02 Nov 2003 05:07:02 GMT
pepper      2003/11/01 21:07:02

  Modified:    docs/manual/mod mod_auth_digest.xml
  A few more typos.
  Revision  Changes    Path
  1.13      +4 -4      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.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- mod_auth_digest.xml	2 Nov 2003 05:02:22 -0000	1.12
  +++ mod_auth_digest.xml	2 Nov 2003 05:07:02 -0000	1.13
  @@ -198,7 +198,7 @@
   <description>Selects the algorithm used to calculate the challenge and
  -response hases in digest authentication</description>
  +response hashes in digest authentication</description>
   <syntax>AuthDigestAlgorithm MD5|MD5-sess</syntax>
   <default>AuthDigestAlgorithm MD5</default>
  @@ -234,10 +234,10 @@
       <p>The <directive>AuthDigestDomain</directive> directive allows
       you to specify one or more URIs which are in the same protection
       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
  +    The specified URIs are prefixes; 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>
  -    including a scheme, host, port, etc) or relative URIs.</p>
  +    including 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.
  @@ -266,7 +266,7 @@
       <p>The <directive>AuthDigestShmemSize</directive> directive defines
       the amount of shared memory, that will be allocated at the server
       startup for keeping track of clients. Note that the shared memory
  -    segment cannot be set less than the space that is neccessary for
  +    segment cannot be set less than the space that is necessary for
       tracking at least <em>one</em> client. This value is dependant on your
       system. If you want to find out the exact value, you may simply
       set <directive>AuthDigestShmemSize</directive> to the value of

View raw message