Sarven Capadisli

This issue is getting out of hand. We have the title saying one thing, the first comment is about something else .. then we are talking about what Control entails.....

There is now a PR that introduces the "owner" concept and requirements: https://github.com/solid/specification/pull/264 . The outcome of that PR should address this issue and be implemented in NSS. The key...

Same behaviour with OPTIONS.

I haven't backtracked this/related issue, .. but the 500 just caught my eye. Why not 415?

>My testing currently shows that PUT without a specified content-type sets the content-type to text/plain and POST with no content-type sets the content type to application/octet-stream. Both should fail with...

Servers can potentially respond with 405 on any resource. 405 is a special case for the root container and the directly associated ACL resource for authorized requests. 403 can come...

https://solidproject.org/TR/2021/protocol-20211217#storage is the relevant section where there is a server requirement to advertise a Link relation type Storage and client requirements to discover the storage in which a resource is...

https://github.com/solid/web-access-control-spec#referring-to-the-acl-resource-itself doesn't actually restrict the possibility of implementations to advertise ACLs of ACLs. The current draft of the Solid spec doesn't either so there is indeed the possibility of implementations...

I think the name "test.jpg" should remain opaque even if the original representation was provided with image/jpeg. That will at least have test.jpg available in JPEG. Subsequent requests with image/jpeg...

The spec does not prohibit a Storage at example.com/ in addition to user.example.com/ . The constraint is so to not have overlapping URI paths. That's all.