Nathan wrote:
mike amundsen wrote:
<snip from Kingsley>
(the resource URL is discoverable via Link: response headers):
</snip>
<snip from Nathan>
try:
https://ods-qa.openlinksw.com/home/dav/Public/fao_to_sumo_mappings.txt,acl
</snip>
Hopefully, the irony is not lost here.
Kingsley's message listed a URI of a resource; the LInk header of
which pointed to the URI of the ACL resource.
IOW, I was given rights to the ACL resource, but not the resource
controlled by that ACL resource.
Thus, "Discovering the ACL resource via the Link Header" *was not
possible*.
So I must ask, Nathan, how did you know the URI of the ACL resource?
What have I missed?
nothing, the demo should have let you have access to both the resource
and the ACL, why you didn't I'm not sure - defer to Kinglsey on that
one ;)
Yes, you could have just added Mike to the resource ACL since you where
the only member with privs on both resources :-)
Anyway, fixed now as I don't think my message was clear enough etc..
Best,
Nathan
--
Regards,
Kingsley Idehen
President & CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen
