search

read-write-web / rww-play

read write web Play
59 stars 19 forks source link

What do we do when a resource claims to have an ACL that doesn't exist #69

Open slorber opened 10 years ago

slorber commented 10 years ago

Currently this produces a server error: rww.ldp.LDPExceptions$ResourceDoesNotExist: no resource for 'cat4.acl'

Is there a "default" behavior? Do we need distinct cases when the acl is offline or unavailable, and when the acl is simply "not found"?

bblfish commented 10 years ago

Was this resource created by hand? My guess is that in that case we should create one. Creating a resource using HTTP should create an acl that contains a wac:include of the LDPC acl. Now interestingly the seems to indicate that ACLs should not be deletable ( or that if deleted they just get automatically created again with default values ).

slorber commented 10 years ago

This was a bug on binary rources because the acl file was xxx.acm.jpg instead of xxx.acl.ttl so the acl was not found

But anyway when a resource have an acl file which is on another server we do not control, this server could be down or could remove the acl file and I wonder what is supposed to be the effect on our local resource: does it become unprotected, or unaccessible or something else?

bblfish commented 10 years ago

Ah well that is perhaps a good reason not to have the HTTP header have a Link: <...>; rel=acl that points to files on another file system. What is said in the header is what the web server is responsible for. So it should control the acl file.

We do allow the inclusion of acls that could be on other file systems though. And if those cannot be accessed, then the server has to work without that information. That seems fine.