Currently NSS reserves .acl for acl resources, and it correctly rejects put requests to it, when there is no subject resource.
But when one do a put request like a/b/c.acl/d/e.txt, it returns success and creates intermediate container a/b/c.acl/, which will be conflict. And then after when one do get over a/b/ it doesn't list that created c.acl/ container, as it treats it as acl resource.
Also may be related: CommunitySolidServer/CommunitySolidServer#1283
Currently NSS reserves
.aclfor acl resources, and it correctly rejects put requests to it, when there is no subject resource.But when one do a put request like
a/b/c.acl/d/e.txt, it returns success and creates intermediate containera/b/c.acl/, which will be conflict. And then after when one do get overa/b/it doesn't list that createdc.acl/container, as it treats it as acl resource.Also may be related: CommunitySolidServer/CommunitySolidServer#1283