This module implements HTTP Digest Authentication
(RFC2617), and
provides an alternative to
To use MD5 Digest authentication, configure the location to be protected as shown in the below example:
The pasword file referenced in the
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
The file
provider is implemented
by the
See
The auth
will
only do authentication (username/password); auth-int
is
authentication plus integrity checking (an MD5 hash of the entity
is also computed and checked); none
will cause the module
to use the old RFC-2069 digest algorithm (which does not include
integrity checking). Both auth
and auth-int
may
be specified, in which the case the browser will choose which of
these to use. none
should only be used if the browser for
some reason does not like the challenge it receives otherwise.
auth-int
is not implemented yet.
The stale=true
. If seconds is
greater than 0 then it specifies the amount of time for which the
nonce is valid; this should probably never be set to less than 10
seconds. If seconds is less than 0 then the nonce never
expires.
The
MD5-sess
is not correctly implemented yet.
The
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
The URIs specified can also point to different servers, in which case clients (which understand this) will then share username/password info across multiple servers without prompting the user each time.
The 0
and read the error message after trying to start the
server.
The size is normally expressed in Bytes, but you
may follow the number with a K
or an M
to
express your value as KBytes or MBytes. For example, the following
directives are all equivalent: