Document the WAC-Allow header in the spec. · Issue #181 · solid/specification · GitHub
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.

Sign up for GitHub

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

Jump to bottom

Document the WAC-Allow header in the spec. #181

Closed
timbl opened this issue Aug 14, 2019 · 5 comments
Closed

Document the WAC-Allow header in the spec. #181

timbl opened this issue Aug 14, 2019 · 5 comments
Labels
doc: Web Access Control topic: resource access
Milestone
~First Public Wor...

Comments

@timbl
Copy link
Contributor

timbl commented Aug 14, 2019

This allows client code to be smart about whether to give the user editing interfaces to data or just view interfaces.

It also allows them to know whether it open to the public, which might affect for example, whether the user is invited to make a public link, like, bookmark, etc of the resource.
@RubenVerborgh
Copy link
Contributor

A draft is at https://github.com/solid/solid-spec/blob/103b1e027356bd525e4cad0138e8288f4881df39/api-rest.md#wac-allow-headers

@timbl
Copy link
Contributor Author

timbl commented Aug 14, 2019

It says "If 'write' is present then 'append' should also be present." but "If write is present, Append is implied" would be more like the ACL spec, I thought.

@RubenVerborgh
Copy link
Contributor

Agreed. It's not very normative at the moment, an explicit link to ACL should be made.

@csarven
Copy link
Member

csarven commented May 5, 2020

Transfering this issue to solid/specification . For the most part it is a duplicate of #170 but keeping it open for the time being.

@csarven csarven closed this as completed May 5, 2020
@csarven csarven transferred this issue from solid/solid-spec May 5, 2020
@csarven csarven reopened this May 5, 2020
@csarven csarven mentioned this issue Nov 15, 2020
Merged
@csarven
Copy link
Member

csarven commented Nov 29, 2020

Proposal/requirements merged via PR #210 . See further details/discussion on concerns of this header, as well as use cases for different permission groups. Implementation feedback is always useful/welcome. Please follow up with new issues/proposals.

@csarven csarven closed this as completed Nov 29, 2020
@csarven csarven added this to the ~First Public Working Draft milestone Nov 29, 2020
@csarven csarven mentioned this issue Jun 17, 2021
Merged
@csarven csarven moved this to Done in Specification Sep 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
doc: Web Access Control topic: resource access
Projects
Specification
Status: Done
Milestone
~First Public Working Draft
Development

No branches or pull requests
3 participants
@csarven @RubenVerborgh @timbl