[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

per-path authz and locking

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-12-14 18:35:49 CET

I'm putting authz_read calls into mod_dav_svn's new locking functions,
so that we can continue the tradition of dealing with unreadable paths.

I'm not sure how mod_dav_svn should behave, though, in these scenarios:

* a request comes to LOCK/UNLOCK an unreadable file path.
   What should mod_dav_svn return?

         - "404 Path Not Found"?
         - "403 Forbidden"?
         - "401 Unauthorized"?

* a request comes in to discover an existing lock on an unreadable path.
   What should mod_dav_svn return?

         - "no lock present" (even if there is)
         - one of the other three 4XX errors above?

* a request comes in to discover all locks below a directory path.
   But some of those locked child-paths are unreadable. What should we
return?

         - only the readable locked-paths (& locks) ?
         - some sort of 4XX error?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 14 18:38:04 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.