Add support for stale directive for digest authenticator #80
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi studio-b12 members !
First of all, I'd like to thank you for this wonderful/easy-to-use Webdav Go package 😃
I'm opening this PR because I recently faced an issue trying to connect to a Webdav server using Digest auth mechanism.
Client successfully connected to this server using digest authenticator, but after some time it was rejected by the server with 401 status codes.
I took a look at the RFC2617 (Section
3.2.1 The WWW-Authenticate Response Header
), and it seems that the server can invalidate the generatednonce
value after some time (which is my case). However, in such case, thestale
directive is added to theWWW-Authenticate
header, indicating to the client to re-authenticate without reprompting the user for username and password.So I forked your project and did a small change in the
Verify
method of theDigestAuth
authenticator to handle such case. I thought you might be interested with these changes 😉