New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ACL gives 403 forbidden when using absolute path in acl:accessTo predicate #76

Open

ghanemabdo opened this issue May 16, 2016 · 0 comments

ghanemabdo commented May 16, 2016 •

edited

Loading

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?

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment