-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
better HTTP DIGEST support #730
Conversation
Cool, thanks! Is this comment still accurate? Is RFC 2617 fully implemented now? If not, which parts remain? Can you add some tests for the additional functionality? (How about a test where the server sends |
…or compatible mode
Hi, I reviewed RFC2617 and did what I can which should be better than before. Listed remaining TODO items as far as I can tell, including less important ones. Added a test case (spent much time to find out RFC2069 has a errata.) |
Looks good. I think we could use some more tests for digest auth (for example, test the actual values of the response hash in different situations, rather than just checking that it is in the right format) but this is an improvement. |
Thanks for merging. Yeah, that was also my original idea to use actual values until I found the errata, which made me exhausted... |
Any chance you want to push 2.29.1 with this pull request? I can't access an API with digest auth using 2.29.0 as the server sends |
By the way, this reminds me of something. We should make the regex more robust like the following.
@nylen would you do this? |
better HTTP DIGEST support
This PR fixes followings:
Ref: http://www.ietf.org/rfc/rfc2617.txt