<directivesynopsis>
<name>AuthDigestAlgorithm</name>
<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>
<contextlist><context>directory</context><context>.htaccess</context>
<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.
<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