Ah, you’ve changed the scope of your
question. J So long as you leverage an Apache authorization
module with user and group permissions, I would think you could control
permissions on who can do what per directory easily, but for this solution, you
would not give both groups WebDAV access. One group (read only) could browse the web
server and download contents of the autogenerated directory while the other
group would be authenticated to have WebDAV privileges. It’s simpler to
manage and granular to the directory, but not exactly what you are asking for
because not both groups are given WebDAV permissions. So the read only group
could not do a select all files to download, much like a network drive
operation, unless they used some sort of browser enhancement. Configuration would be something like (I’m
doing this off the top of my head for illustration, please don’t expect
to cut and paste this without syntax correction and adaptation for your
situation): <Directory "/www/docroot/projects/X"> Options Indexes AllowOverride None AuthType Basic AuthName "Only group X can
publish!" AuthUserFile /home/www/acl/htpasswdfile AuthGroupFile /home/www/acl/groupfile DAV On <LimitExcept GET HEAD
OPTIONS> Require group X </LimitExcept> </Directory> --Mark Mark Lavi, mailto:mlavi@xxxxxxx || phone:+1-650-933-7707 From: Todd Hivnor
[mailto:spambox_98103@xxxxxxxxx] Updating the permissions on the file system will work for folders which
are strictly read-only. But in a lot of cases, I want the folder to be readable
by group X and writable by group Y. --Mark Mark Lavi, SGI mailto:mlavi@xxxxxxx || phone:+1-650-933-7707 From: Todd Hivnor
[mailto:spambox_98103@xxxxxxxxx] I am running WebDAV on my Apache 2.0.51 server on Fedora Core 2. configure this? It seems like a fairly basic
Everyone is raving about the
all-new Yahoo! Mail beta. |