W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > October to December 2004


From: Lisa Dusseault <lisa@osafoundation.org>
Date: Mon, 15 Nov 2004 09:07:36 -0800
Message-Id: <D9651581-3728-11D9-A8FA-000A95B2BB72@osafoundation.org>
Cc: "<acl@webdav.org>" <acl@webdav.org>, "<www-webdav-dasl@w3.org> <www-webdav-dasl@w3.org>" <www-webdav-dasl@w3.org>
To: <Heiko.Weber@softwareag.com>

CC'ing the DASL mailing list...  Since ACL is already RFC and SEARCH is 
not, guidance on this topic should go into the SEARCh draft.


On Nov 15, 2004, at 1:14 AM, <Heiko.Weber@softwareag.com> wrote:

> Hello everyone,
> I have a question about the expected behavior of a WebDAV server, when
> resources are being searched that have ACLs defined on them. If I am
> searching through the resources in a collection and I'm not allowed to
> read the searched information on some of the resources, should the
> server simply ignore these resources and only list the URIs of the
> matching documents that were allowed to be read, or should the server
> explicitly say, that certain documents were not readable, similar to 
> the
> result of the Unix "find" command that also lists all the directories
> which it had no access to?
> If I have a <DAV:deny><DAV:privilege><DAV:all
> /></DAV:privilege></DAV:deny> defined on a resource for a certain user 
> -
> should a SEARCH with a query-schema-discovery document on that resource
> return something for that user, or rather just an HTTP 403?
> regards,
>    Heiko Weber
> _______________________________________________
> acl mailing list
> acl@webdav.org
> http://mailman.webdav.org/mailman/listinfo/acl
Received on Monday, 15 November 2004 17:10:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:10 GMT