]> git.ipfire.org Git - thirdparty/squid.git/commit
projects / thirdparty / squid.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 9abb716) | patch
Random authenticaiton failures when using Digest authentication
authorhno <>
Sun, 30 Dec 2007 11:06:30 +0000 (11:06 +0000)
committerhno <>
Sun, 30 Dec 2007 11:06:30 +0000 (11:06 +0000)
commit9f70982412dab8246fdec5ddd4a52f9d360b4177
tree06b5c9b5b7c704845518b210d3baa01995861a78tree
parent9abb716f294709635b8b8355573300f316c8311fcommit | diff
Random authenticaiton failures when using Digest authentication

The stale= propery of the Digest responses sent by Squid indicated far
too often that the nonce was not stale. Contrary to what the RFC recommends
we should only say that the nonce is not stale when it is a valid nonce but
the response did not compute (invalid user or password). In all other
situations we should say that the nonce is stale even if we haven't
validated the response.
src/auth/digest/auth_digest.cc diff | blob | blame | history
src/auth/digest/auth_digest.h diff | blob | blame | history
Mirror of https://github.com/squid-cache/squid.git