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

Behavior of index.html and access control #163

Closed
RubenVerborgh opened this issue Jan 29, 2021 · 1 comment
Closed

Behavior of index.html and access control #163

RubenVerborgh opened this issue Jan 29, 2021 · 1 comment

Comments

@RubenVerborgh
Copy link
Contributor

RubenVerborgh commented Jan 29, 2021

No description provided.

@csarven
Copy link
Member

csarven commented Jan 29, 2021

I wonder as well, beyond this:

When an authorized GET request to / is given a 200 response with Content-Location: ./index.html, then we know ./index.html is a representation of ./. They have the same access privileges. OPTIONS would be a 204. For the other request methods, the Protocol includes:

When a PUT, POST, PATCH or DELETE method request targets a representation URL that is different than the resource URL, the server MUST respond with a 307 or 308 status code and Location header specifying the preferred URI reference.

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

2 participants