You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Edson Lidorio - Listas <ed...@gmail.com> on 2009/02/07 01:17:16 UTC

could not open the requested SVN filesystem

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<span class="Apple-style-span"
 style="border-collapse: separate; color: rgb(0, 0, 0); font-family: -webkit-monospace; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;">Hi,<br>
<br>
I am setting up my apache with subversion server is generating this
error below:<span class="Apple-converted-space">&nbsp;</span><br>
Could not open the requested SVN filesystem<span
 class="Apple-converted-space">&nbsp;</span><br>
Is attached: dav_svn.conf<br>
<br>
<br>
# dav_svn.conf - Example Subversion/Apache configuration<br>
#<br>
# For details and further options see the Apache user manual and<br>
# the Subversion book.<br>
#<br>
# NOTE: for a setup with multiple vhosts, you will want to do this<br>
# configuration in /etc/apache2/sites-available/*, not here.<br>
<br>
# &lt;Location URL&gt; ... &lt;/Location&gt;<br>
# URL controls how the repository appears to the outside world.<br>
# In this example clients access the repository as <a class="moz-txt-link-freetext" href="http://hostname/svn/">http://hostname/svn/</a><br>
# Note, a literal /svn should NOT exist in your document root.<br>
&lt;Location /svnrepo&gt;<br>
&nbsp; # Uncomment this to enable the repository<br>
&nbsp; DAV svn<br>
&nbsp; # Set this to the path to your repository<br>
&nbsp; #SVNPath /srv/svnrepo<br>
&nbsp; # Alternatively, use SVNParentPath if you have multiple repositories
under<br>
&nbsp; # under a single directory (/var/lib/svn/repo1, /var/lib/svn/repo2,
...).<br>
&nbsp; # You need either SVNPath and SVNParentPath, but not both.<br>
&nbsp; SVNParentPath /srv/svnrepo/meusdoc<br>
&nbsp; #SVNParentPath /srv/svnrepo/apostila<br>
&nbsp; # Access control is done at 3 levels: (1) Apache authentication, via<br>
&nbsp; # any of several methods.&nbsp; A "Basic Auth" section is commented out<br>
&nbsp; # below.&nbsp; (2) Apache &lt;Limit&gt; and &lt;LimitExcept&gt;, also
commented out<br>
&nbsp; # below.&nbsp; (3) mod_authz_svn is a svn-specific authorization module<br>
&nbsp; # which offers fine-grained read/write access control for paths<br>
&nbsp; # within a repository.&nbsp; (The first two layers are coarse-grained; you<br>
&nbsp; # can only enable/disable access to an entire repository.)&nbsp; Note that<br>
&nbsp; # mod_authz_svn is noticeably slower than the other two layers, so if<br>
&nbsp; # you don't need the fine-grained control, don't configure it.<br>
&nbsp; # Basic Authentication is repository-wide.&nbsp; It is not secure unless<br>
&nbsp; # you are using https.&nbsp; See the 'htpasswd' command to create and<br>
&nbsp; # manage the password file - and the documentation for the<br>
&nbsp; # 'auth_basic' and 'authn_file' modules, which you will need for this<br>
&nbsp; # (enable them with 'a2enmod').<br>
&nbsp; AuthType Basic<br>
&nbsp; AuthName "Server Ubuntu - Linux - Reposit&oacute;rio"<br>
&nbsp; AuthUserFile /etc/apache2/dav_svn.passwd<br>
&nbsp; # To enable authorization via mod_authz_svn<br>
&nbsp; AuthzSVNAccessFile /etc/apache2/dav_svn.authz<br>
&nbsp; # The following three lines allow anonymous read, but make<br>
&nbsp; # committers authenticate themselves.&nbsp; It requires the 'authz_user'<br>
&nbsp; # module (enable it with 'a2enmod').<br>
&nbsp; #&lt;LimitExcept GET PROPFIND OPTIONS REPORT&gt;<br>
&nbsp;&nbsp;&nbsp; Require valid-user<br>
&nbsp; #&lt;/LimitExcept&gt; <br>
&lt;/Location&gt;<br>
<br>
</span>
</body>
</html>

Re: could not open the requested SVN filesystem

Posted by Edson Lidorio - Listas <ed...@gmail.com>.
Hi Ryan,

I checked the documentation as you passed the link in previous email.

Crieu the groups and the repository, generating this error log:
Path of my repository:
/ srv / svnrepo / cpdlazarus
/ srv / svnrepo / projects

[groups]
desenvolvedores = lidorio
analistas = linux


#repository cpdlazarus
[cpdlazarus:/srv/svnrepo/cpdlazarus]
@desenvolvedores = rw
@analista = r

#repository projetos
[projetos:/srv/svnrepo/projetos]
@analistas = rw


Error

Obter arquivo http://192.168.0.4:8080/svnrepo/cpdlazarus, revisão HEAD, 
Completamente recursivo, Projetos externos incluidos
Servidor enviou valor de retorno inválido (403 Forbidden) na resposta a 
OPTIONS
pedido por 'http://192.168.0.4:8080/svnrepo/cpdlazarus'

Ryan Schmidt escreveu:
>
> On Feb 7, 2009, at 13:32, Edson Lidorio - Listas wrote:
>
>> Ryan Schmidt escreveu:
>>
>>> On Feb 7, 2009, at 13:15, Edson Lidorio - Listas wrote:
>>>
>>>> How to access that he seeks through the folder conf for each 
>>>> repository, through the files and AuthZ passwd? Now this looking 
>>>> for: AuthUserFile / etc/apache2/dav_svn.passwd AuthzSVNAccessFile / 
>>>> etc/apache2/dav_svn.authz
>>>
>>> I believe all repositories will share the same authz setup. If you 
>>> want separate authz setups, you cannot have them in a single 
>>> <Location> block. But maybe I should first ask why you want to have 
>>> separate authz files for each repository.
>>
>>>
>> Why do I have some projects to develop access and other projects have 
>> not. I would like to limit access to repository! How?
>
>
> A single authz config file can describe restrictions for different 
> repositories. See this part of the book:
>
> http://svnbook.red-bean.com/en/1.5/svn.serverconfig.pathbasedauthz.html
>
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1125101

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].


Re: could not open the requested SVN filesystem

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Feb 7, 2009, at 13:32, Edson Lidorio - Listas wrote:

> Ryan Schmidt escreveu:
>
>> On Feb 7, 2009, at 13:15, Edson Lidorio - Listas wrote:
>>
>>> How to access that he seeks through the folder conf for each  
>>> repository, through the files and AuthZ passwd? Now this looking  
>>> for: AuthUserFile / etc/apache2/dav_svn.passwd  
>>> AuthzSVNAccessFile / etc/apache2/dav_svn.authz
>>
>> I believe all repositories will share the same authz setup. If you  
>> want separate authz setups, you cannot have them in a single  
>> <Location> block. But maybe I should first ask why you want to  
>> have separate authz files for each repository.
>
>>
> Why do I have some projects to develop access and other projects  
> have not. I would like to limit access to repository! How?


A single authz config file can describe restrictions for different  
repositories. See this part of the book:

http://svnbook.red-bean.com/en/1.5/svn.serverconfig.pathbasedauthz.html

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1120552

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: could not open the requested SVN filesystem

Posted by Edson Lidorio - Listas <ed...@gmail.com>.
Why do I have some projects to develop access and other projects have not. 
I would like to limit access to repository! How?

Ryan Schmidt escreveu:
>
> On Feb 7, 2009, at 13:15, Edson Lidorio - Listas wrote:
>
>> How to access that he seeks through the folder conf for each 
>> repository, through the files and AuthZ passwd? Now this looking for: 
>> AuthUserFile / etc/apache2/dav_svn.passwd AuthzSVNAccessFile / 
>> etc/apache2/dav_svn.authz
>
> I believe all repositories will share the same authz setup. If you 
> want separate authz setups, you cannot have them in a single 
> <Location> block. But maybe I should first ask why you want to have 
> separate authz files for each repository.
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1120545

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: could not open the requested SVN filesystem

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Feb 7, 2009, at 13:15, Edson Lidorio - Listas wrote:

> How to access that he seeks through the folder conf for each  
> repository, through the files and AuthZ passwd? Now this looking  
> for: AuthUserFile / etc/apache2/dav_svn.passwd AuthzSVNAccessFile /  
> etc/apache2/dav_svn.authz

I believe all repositories will share the same authz setup. If you  
want separate authz setups, you cannot have them in a single  
<Location> block. But maybe I should first ask why you want to have  
separate authz files for each repository.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1120539

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: could not open the requested SVN filesystem

Posted by Edson Lidorio - Listas <ed...@gmail.com>.
Hello Ryan Schmidt, 

Thanks, it worked .... 
I need one more thing. 
How to access that he seeks through the folder 
conf for each repository, through the files and AuthZ passwd? Now this 
looking for: 
AuthUserFile / etc/apache2/dav_svn.passwd 
AuthzSVNAccessFile / etc/apache2/dav_svn.authz 

I appreciate any help; 
Edson

Ryan Schmidt escreveu:
> On Feb 7, 2009, at 12:25, Edson Lidorio - Listas wrote:
>
>> Ryan Schmidt escreveu:
>>
>>> On Feb 6, 2009, at 19:17, Edson Lidorio - Listas wrote:
>>>
>>>> I am setting up my apache with subversion server is generating this 
>>>> error below:
>>>> Could not open the requested SVN filesystem
>>>
>>> Generally this means your Apache is not pointing to where your 
>>> repository exists on disk. Where is the repository on disk -- what 
>>> is the path that you "svnadmin create"d -- the path that now 
>>> contains the items README.txt, conf, dav, db, format, hooks, locks?
>>
>> I have a directory where I create all repository
>> in: /srv/svnrepo                 #home directory
>>  /srv/svnrepo/meusdoc  #repository  /srv/svnrepo/teste       #repository
>>
>> even so he does not believe, please check my file dav_svn.conf what 
>> is wrong there?
>
> Then you need "SVNParentPath /srv/svnrepo"
> and not "SVNParentPath /srv/svnrepo/meusdoc"
>
>
>>>> Is attached: dav_svn.conf
>>>>
>>>>
>>>> # dav_svn.conf - Example Subversion/Apache configuration
>>>> #
>>>> # For details and further options see the Apache user manual and
>>>> # the Subversion book.
>>>> #
>>>> # NOTE: for a setup with multiple vhosts, you will want to do this
>>>> # configuration in /etc/apache2/sites-available/*, not here.
>>>>
>>>> # <Location URL> ... </Location>
>>>> # URL controls how the repository appears to the outside world.
>>>> # In this example clients access the repository as 
>>>> http://hostname/svn/
>>>> # Note, a literal /svn should NOT exist in your document root.
>>>> <Location /svnrepo>
>>>>   # Uncomment this to enable the repository
>>>>   DAV svn
>>>>   # Set this to the path to your repository
>>>>   #SVNPath /srv/svnrepo
>>>>   # Alternatively, use SVNParentPath if you have multiple 
>>>> repositories under
>>>>   # under a single directory (/var/lib/svn/repo1, 
>>>> /var/lib/svn/repo2, ...).
>>>>   # You need either SVNPath and SVNParentPath, but not both.
>>>>   SVNParentPath /srv/svnrepo/meusdoc
>>>>   #SVNParentPath /srv/svnrepo/apostila
>>>>   # Access control is done at 3 levels: (1) Apache authentication, via
>>>>   # any of several methods.  A "Basic Auth" section is commented out
>>>>   # below.  (2) Apache <Limit> and <LimitExcept>, also commented out
>>>>   # below.  (3) mod_authz_svn is a svn-specific authorization module
>>>>   # which offers fine-grained read/write access control for paths
>>>>   # within a repository.  (The first two layers are coarse-grained; 
>>>> you
>>>>   # can only enable/disable access to an entire repository.)  Note 
>>>> that
>>>>   # mod_authz_svn is noticeably slower than the other two layers, 
>>>> so if
>>>>   # you don't need the fine-grained control, don't configure it.
>>>>   # Basic Authentication is repository-wide.  It is not secure unless
>>>>   # you are using https.  See the 'htpasswd' command to create and
>>>>   # manage the password file - and the documentation for the
>>>>   # 'auth_basic' and 'authn_file' modules, which you will need for 
>>>> this
>>>>   # (enable them with 'a2enmod').
>>>>   AuthType Basic
>>>>   AuthName "Server Ubuntu - Linux - Repositório"
>>>>   AuthUserFile /etc/apache2/dav_svn.passwd
>>>>   # To enable authorization via mod_authz_svn
>>>>   AuthzSVNAccessFile /etc/apache2/dav_svn.authz
>>>>   # The following three lines allow anonymous read, but make
>>>>   # committers authenticate themselves.  It requires the 'authz_user'
>>>>   # module (enable it with 'a2enmod').
>>>>   #<LimitExcept GET PROPFIND OPTIONS REPORT>
>>>>     Require valid-user
>>>>   #</LimitExcept>
>>>> </Location>
>
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1120512

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].


Re: could not open the requested SVN filesystem

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Feb 7, 2009, at 12:25, Edson Lidorio - Listas wrote:

> Ryan Schmidt escreveu:
>
>> On Feb 6, 2009, at 19:17, Edson Lidorio - Listas wrote:
>>
>>> I am setting up my apache with subversion server is generating  
>>> this error below:
>>> Could not open the requested SVN filesystem
>>
>> Generally this means your Apache is not pointing to where your  
>> repository exists on disk. Where is the repository on disk -- what  
>> is the path that you "svnadmin create"d -- the path that now  
>> contains the items README.txt, conf, dav, db, format, hooks, locks?
>
> I have a directory where I create all repository
> in: /srv/svnrepo                 #home directory
>  /srv/svnrepo/meusdoc  #repository  /srv/svnrepo/teste        
> #repository
>
> even so he does not believe, please check my file dav_svn.conf what  
> is wrong there?

Then you need "SVNParentPath /srv/svnrepo"
and not "SVNParentPath /srv/svnrepo/meusdoc"


>>> Is attached: dav_svn.conf
>>>
>>>
>>> # dav_svn.conf - Example Subversion/Apache configuration
>>> #
>>> # For details and further options see the Apache user manual and
>>> # the Subversion book.
>>> #
>>> # NOTE: for a setup with multiple vhosts, you will want to do this
>>> # configuration in /etc/apache2/sites-available/*, not here.
>>>
>>> # <Location URL> ... </Location>
>>> # URL controls how the repository appears to the outside world.
>>> # In this example clients access the repository as http:// 
>>> hostname/svn/
>>> # Note, a literal /svn should NOT exist in your document root.
>>> <Location /svnrepo>
>>>   # Uncomment this to enable the repository
>>>   DAV svn
>>>   # Set this to the path to your repository
>>>   #SVNPath /srv/svnrepo
>>>   # Alternatively, use SVNParentPath if you have multiple  
>>> repositories under
>>>   # under a single directory (/var/lib/svn/repo1, /var/lib/svn/ 
>>> repo2, ...).
>>>   # You need either SVNPath and SVNParentPath, but not both.
>>>   SVNParentPath /srv/svnrepo/meusdoc
>>>   #SVNParentPath /srv/svnrepo/apostila
>>>   # Access control is done at 3 levels: (1) Apache  
>>> authentication, via
>>>   # any of several methods.  A "Basic Auth" section is commented out
>>>   # below.  (2) Apache <Limit> and <LimitExcept>, also commented out
>>>   # below.  (3) mod_authz_svn is a svn-specific authorization module
>>>   # which offers fine-grained read/write access control for paths
>>>   # within a repository.  (The first two layers are coarse- 
>>> grained; you
>>>   # can only enable/disable access to an entire repository.)   
>>> Note that
>>>   # mod_authz_svn is noticeably slower than the other two layers,  
>>> so if
>>>   # you don't need the fine-grained control, don't configure it.
>>>   # Basic Authentication is repository-wide.  It is not secure  
>>> unless
>>>   # you are using https.  See the 'htpasswd' command to create and
>>>   # manage the password file - and the documentation for the
>>>   # 'auth_basic' and 'authn_file' modules, which you will need  
>>> for this
>>>   # (enable them with 'a2enmod').
>>>   AuthType Basic
>>>   AuthName "Server Ubuntu - Linux - Repositório"
>>>   AuthUserFile /etc/apache2/dav_svn.passwd
>>>   # To enable authorization via mod_authz_svn
>>>   AuthzSVNAccessFile /etc/apache2/dav_svn.authz
>>>   # The following three lines allow anonymous read, but make
>>>   # committers authenticate themselves.  It requires the  
>>> 'authz_user'
>>>   # module (enable it with 'a2enmod').
>>>   #<LimitExcept GET PROPFIND OPTIONS REPORT>
>>>     Require valid-user
>>>   #</LimitExcept>
>>> </Location>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1120418

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].


Re: could not open the requested SVN filesystem

Posted by Edson Lidorio - Listas <ed...@gmail.com>.
I have a directory where I create all repository
in: 
/srv/svnrepo                 #home directory
  /srv/svnrepo/meusdoc  #repository 
  /srv/svnrepo/teste       #repository

even so he does not believe, please check my file dav_svn.conf what is 
wrong there?


--
Edson

Ryan Schmidt escreveu:
>
> On Feb 6, 2009, at 19:17, Edson Lidorio - Listas wrote:
>
>> I am setting up my apache with subversion server is generating this 
>> error below:
>> Could not open the requested SVN filesystem
>
> Generally this means your Apache is not pointing to where your 
> repository exists on disk. Where is the repository on disk -- what is 
> the path that you "svnadmin create"d -- the path that now contains the 
> items README.txt, conf, dav, db, format, hooks, locks?
>
>
>
>> Is attached: dav_svn.conf
>>
>>
>> # dav_svn.conf - Example Subversion/Apache configuration
>> #
>> # For details and further options see the Apache user manual and
>> # the Subversion book.
>> #
>> # NOTE: for a setup with multiple vhosts, you will want to do this
>> # configuration in /etc/apache2/sites-available/*, not here.
>>
>> # <Location URL> ... </Location>
>> # URL controls how the repository appears to the outside world.
>> # In this example clients access the repository as http://hostname/svn/
>> # Note, a literal /svn should NOT exist in your document root.
>> <Location /svnrepo>
>>   # Uncomment this to enable the repository
>>   DAV svn
>>   # Set this to the path to your repository
>>   #SVNPath /srv/svnrepo
>>   # Alternatively, use SVNParentPath if you have multiple 
>> repositories under
>>   # under a single directory (/var/lib/svn/repo1, /var/lib/svn/repo2, 
>> ...).
>>   # You need either SVNPath and SVNParentPath, but not both.
>>   SVNParentPath /srv/svnrepo/meusdoc
>>   #SVNParentPath /srv/svnrepo/apostila
>>   # Access control is done at 3 levels: (1) Apache authentication, via
>>   # any of several methods.  A "Basic Auth" section is commented out
>>   # below.  (2) Apache <Limit> and <LimitExcept>, also commented out
>>   # below.  (3) mod_authz_svn is a svn-specific authorization module
>>   # which offers fine-grained read/write access control for paths
>>   # within a repository.  (The first two layers are coarse-grained; you
>>   # can only enable/disable access to an entire repository.)  Note that
>>   # mod_authz_svn is noticeably slower than the other two layers, so if
>>   # you don't need the fine-grained control, don't configure it.
>>   # Basic Authentication is repository-wide.  It is not secure unless
>>   # you are using https.  See the 'htpasswd' command to create and
>>   # manage the password file - and the documentation for the
>>   # 'auth_basic' and 'authn_file' modules, which you will need for this
>>   # (enable them with 'a2enmod').
>>   AuthType Basic
>>   AuthName "Server Ubuntu - Linux - Repositório"
>>   AuthUserFile /etc/apache2/dav_svn.passwd
>>   # To enable authorization via mod_authz_svn
>>   AuthzSVNAccessFile /etc/apache2/dav_svn.authz
>>   # The following three lines allow anonymous read, but make
>>   # committers authenticate themselves.  It requires the 'authz_user'
>>   # module (enable it with 'a2enmod').
>>   #<LimitExcept GET PROPFIND OPTIONS REPORT>
>>     Require valid-user
>>   #</LimitExcept>
>> </Location>
>
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1120391

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].


Re: could not open the requested SVN filesystem

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Feb 6, 2009, at 19:17, Edson Lidorio - Listas wrote:

> I am setting up my apache with subversion server is generating this  
> error below:
> Could not open the requested SVN filesystem

Generally this means your Apache is not pointing to where your  
repository exists on disk. Where is the repository on disk -- what is  
the path that you "svnadmin create"d -- the path that now contains  
the items README.txt, conf, dav, db, format, hooks, locks?



> Is attached: dav_svn.conf
>
>
> # dav_svn.conf - Example Subversion/Apache configuration
> #
> # For details and further options see the Apache user manual and
> # the Subversion book.
> #
> # NOTE: for a setup with multiple vhosts, you will want to do this
> # configuration in /etc/apache2/sites-available/*, not here.
>
> # <Location URL> ... </Location>
> # URL controls how the repository appears to the outside world.
> # In this example clients access the repository as http://hostname/ 
> svn/
> # Note, a literal /svn should NOT exist in your document root.
> <Location /svnrepo>
>   # Uncomment this to enable the repository
>   DAV svn
>   # Set this to the path to your repository
>   #SVNPath /srv/svnrepo
>   # Alternatively, use SVNParentPath if you have multiple  
> repositories under
>   # under a single directory (/var/lib/svn/repo1, /var/lib/svn/ 
> repo2, ...).
>   # You need either SVNPath and SVNParentPath, but not both.
>   SVNParentPath /srv/svnrepo/meusdoc
>   #SVNParentPath /srv/svnrepo/apostila
>   # Access control is done at 3 levels: (1) Apache authentication, via
>   # any of several methods.  A "Basic Auth" section is commented out
>   # below.  (2) Apache <Limit> and <LimitExcept>, also commented out
>   # below.  (3) mod_authz_svn is a svn-specific authorization module
>   # which offers fine-grained read/write access control for paths
>   # within a repository.  (The first two layers are coarse-grained;  
> you
>   # can only enable/disable access to an entire repository.)  Note  
> that
>   # mod_authz_svn is noticeably slower than the other two layers,  
> so if
>   # you don't need the fine-grained control, don't configure it.
>   # Basic Authentication is repository-wide.  It is not secure unless
>   # you are using https.  See the 'htpasswd' command to create and
>   # manage the password file - and the documentation for the
>   # 'auth_basic' and 'authn_file' modules, which you will need for  
> this
>   # (enable them with 'a2enmod').
>   AuthType Basic
>   AuthName "Server Ubuntu - Linux - Repositório"
>   AuthUserFile /etc/apache2/dav_svn.passwd
>   # To enable authorization via mod_authz_svn
>   AuthzSVNAccessFile /etc/apache2/dav_svn.authz
>   # The following three lines allow anonymous read, but make
>   # committers authenticate themselves.  It requires the 'authz_user'
>   # module (enable it with 'a2enmod').
>   #<LimitExcept GET PROPFIND OPTIONS REPORT>
>     Require valid-user
>   #</LimitExcept>
> </Location>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1117945

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].