You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Lee Harr <mi...@hotmail.com> on 2006/02/12 16:18:44 UTC

allow only selected files through apache/dav

Hi;

I have a subversion repository set up with webdav access through
apache. Developers connect through ssl and use digest auth. That
is working fine.

For a few of the files, I want to allow anonymous browsing.

The problem is that most of the files have a copyright restriction
not allowing open posting on the net. So, I just want to pick 4
files from trunk that will be openly available. (read-only of course)

I am trying to work out the apache configuration magic that will just
allow anonymous access to those 4 files in trunk.

If I do something like this ...

<Location /anon>
        DAV svn
        SVNPath /home/rsvn/repo1/
        SVNPathAuthz off

    <LimitExcept GET PROPFIND OPTIONS REPORT>
        Deny from all
    </LimitExcept>

</Location>

Then the whole repo is available. How can I restrict it so that only
the files control.c, autonomous.c, user_routines.c and user_routines.h
are available?

Thanks for any help.

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: allow only selected files through apache/dav

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Feb 12, 2006, at 17:18, Lee Harr wrote:

> I am trying to work out the apache configuration magic that will just
> allow anonymous access to those 4 files in trunk.

Someone with authz experience will probably be able to give you a  
recipe. But it seems to be like it might be simpler and less  
dangerous if you just put those four files on a web server somewhere,  
outside of your repository, and make those available. You could make  
sure they're always up-to-date by updating them in a post-commit hook  
any time they're modified...




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org