Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Digest auth should implement stale=True #24

Open
kmanley opened this issue Jan 7, 2016 · 1 comment
Open

Digest auth should implement stale=True #24

kmanley opened this issue Jan 7, 2016 · 1 comment

Comments

@kmanley
Copy link
Contributor

kmanley commented Jan 7, 2016

From https://www.ietf.org/rfc/rfc2617.txt

The Authorization header may be included
preemptively; doing so improves server efficiency and avoids extra
round trips for authentication challenges. The server may choose to
accept the old Authorization header information, even though the
nonce value included might not be fresh. Alternatively, the server
may return a 401 response with a new nonce value, causing the client
to retry the request; by specifying stale=TRUE with this response,
the server tells the client to retry with the new nonce, but without
prompting for a new username and password.

Currently CheckAuth just returns if it doesn't find the nonce in its cache. Would be nice to support stale=TRUE.

I will send a PR

@kmanley
Copy link
Contributor Author

kmanley commented Jan 8, 2016

Fixed in e837317

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant