-
Notifications
You must be signed in to change notification settings - Fork 20
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
added the client point of view on UC3 #239
Conversation
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Matthieu Bosquet <[email protected]>
Todo: what is the ACR for | ||
`</weekly-status/2021-04-28/report.md>` and what information is in it? | ||
An unauthenticated client making a GET on `</weekly-status/>` container will receive a `Link: <.acp>; rel="acl"` header in the `401` response that points to the above `<.acp>`. | ||
This relation is what makes the contents of `</weekly-status/.acp>` authoritative, and is therefore the information the client can use to decide what credentials to present. |
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.
I think this assumption can be made only in very limited number of real world scenarios. I don't see why we would want to make this assumption for this use case.
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.
What assumption do you have a problem with @elf-pavlik?
I am building my server this way and that is how I built clients in the past.
Oops, I mistakenly merged this by pushing to the wrong branch on the command line. |
No worries we can still catch issues on the PR targeted by this one. I just moved my comment to #216 (review) |
I agree with @elf-pavlik, no worries Henry. |
No description provided.