ACL gives 403 forbidden when using absolute path in acl:accessTo predicate #76
Description
I tried modifying the authorizations in an acl resource manually. Currently Warp writes the acls having
acl:accessTo <resource1.ttl>
But when changing it to the corresponding absolute path
acl:accessTo <https://example.databox.me/applications/app/resource1.ttl>
It doesn't recognize the authorizations and always throws 403 forbidden!
Is there a reason necessitates using relative paths or this is a bug?