-
Notifications
You must be signed in to change notification settings - Fork 22.6k
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
Update authorisation header and extend www-auth with digest #9014
Conversation
|
||
## Specifications | ||
|
||
| Specification | Title | | ||
| ---------------------------------------------------- | -------------------------------------- | | ||
| {{RFC("7235", "Authorization", "4.2")}} | HTTP/1.1: Authentication | | ||
| {{RFC("7617")}} | The 'Basic' HTTP Authentication Scheme | | ||
| {{RFC("7616")}} | HTTP Digest Access Authentication | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note, I have BCD item in progress to add these. Still under discussion. This is kind of "interim solution".
It doesn't sit well with me that this you still need to go to the spec to get detail. But it is still better than it was/more useful than over-promoting the basic authentication. So, merging. |
This is continued update or HTTP authorisation docs for #8682
This updates the
WWW-Authenticate
andAuthorization
header docs with additional information. These headers are part of a framework, so the directives depend on the authentication method used. Prior to these updates the headers were written as though only theBasic
authentication existed.What I have tried to do is make this framework more obvious by including the directives and examples for both
Basic
andDigest
authentication.Part of the way though though I realised that it is very difficult to do justice to the Digest authentication - yes I could capture the entire algorithm, but the spec is pretty dense. I don't think we want to go to the point where people think this replaces the spec. What I want to do is give an overview that gives a good flavour of how it works, but makes it pretty clear that you do need to go to the spec if you're going to do anything more than superficial.
In other words, I don't think this is perfect, but I think it is better. Thoughts?
This part is pretty much done for now. I am planning on updating the BCD mdn/browser-compat-data#12446 to give better links into the spec. That is actually likely to be the most valuable part of this effort :-0