Open ghanemabdo opened 8 years ago
I tried modifying the authorizations in an acl resource manually. Currently Warp writes the acls having acl:accessTo <resource1.ttl>
acl:accessTo <resource1.ttl>
But when changing it to the corresponding absolute path acl:accessTo <https://example.databox.me/applications/app/resource1.ttl>
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?
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?