You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I delete a file /foo/bar.txt that is controlled by /foo/bar.txt.acl, the .acl file does not get deleted. It becomes invisible because without being able to query /foo/bar.txt's link header, there's no way to know where its .acl should be and .acl files are not discover-able with a GET on a container. This now-unfindable file then prevents us from deleting it's container /foo/ since the container is non-empty and returns 409 on attempt to delete it even though it "looks" empty.
Another problem with this: if I delete /foo/bar.txt but not /foo/bar.txt.acl and I later create /foo/bar.txt - it will be controlled by /foo/bar.txt.acl without me specifically telling it to be.
Activity
jeff-zucker commentedon Apr 26, 2019
Another problem with this: if I delete /foo/bar.txt but not /foo/bar.txt.acl and I later create /foo/bar.txt - it will be controlled by /foo/bar.txt.acl without me specifically telling it to be.
RubenVerborgh commentedon Jun 17, 2019
See solid/solid-spec#157
RubenVerborgh commentedon Jun 18, 2019
Suggested solution: #1179
Alternative solution: https://github.com/solid/solid-spec/issues/190
RubenVerborgh commentedon Jun 23, 2019
Also need to consider security, in https://github.com/solid/solid-spec/issues/196