You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Jeff Jensen <je...@upstairstechnology.com> on 2006/05/15 20:59:25 UTC
"OPTIONS request failed" on commit
Hi,
We temporarily setup svnserve for our new Subversion server (and it works :-),
and now are trying to setup use through Apache. We have it partially working
from remote (e.g. authentication, authorization, svn co, browser traversing),
but cannot commit.
Using:
svn, version 1.1.4 (r13838)
compiled Apr 5 2005, 05:18:28
Apache/2.0.53
We've been pulling our hair out Googling and searching this list's archives etc.
(every thread starts to answer something, but then ends :-( I know there is
some config error on our part. So far we have not determined what it is!
Our best guess so far is there is/are another thing to config in httpd.conf, or
something with our firewall/forwarding. For starters, we understand that the
web-dav OPTIONS command is not working, but not sure how to get
further/troubleshoot and diagnose why.
The core issue to solve is this error:
$ svn commit -m "the msg"
svn: Commit failed (details follow):
svn: OPTIONS request failed on '/svn/mndoc'
svn: The OPTIONS request returned invalid XML in the response: XML parse error
at line 1: no element found (/svn/mndoc)
This is the section added to http.conf
<IfModule mod_dav_svn.c>
<Location /svn>
DAV svn
SVNParentPath /home/subversion/repos
#access control policy
AuthzSVNAccessFile /home/subversion/conf/authorization-apache
#how to authenticate
AuthType Basic
AuthName "Subversion Repository"
AuthUserFile /home/subversion/conf/authentication-apache
#only authenticated users can access
Require valid-user
</Location>
</IfModule>
Anyone have advice for us please?!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: "OPTIONS request failed" on commit
Posted by Jeff Jensen <je...@upstairstechnology.com>.
Still having no luck. I'm getting in trouble with the remote developers
that cannot connect! :-(
Our svn is installed on Linux. To get to it, the requests pass through a MS
ISA Server.
Is anyone else fronting with ISA? If so, can you share any tips for
settings to check that may cause a block or other problem?
If ISA is indeed blocking, it would explain why the browser works (e.g.
GETS) but svn commit does not (OPTIONS blocked).
> -----Original Message-----
> From: Jeff Jensen [mailto:jeffjensen@upstairstechnology.com]
> Sent: Monday, May 15, 2006 10:01 PM
> To: 'Nico Kadel-Garcia'
> Cc: users@subversion.tigris.org
> Subject: RE: "OPTIONS request failed" on commit
>
> Is there something else to do to enable either WebDAV or SVN
> DAV, other than what is in the <Location> block? Trying to
> track down what would disable or block OPTIONS WebDAV method...
>
>
> > -----Original Message-----
> > From: Jeff Jensen [mailto:jeffjensen@upstairstechnology.com]
> > Sent: Monday, May 15, 2006 9:07 PM
> > To: 'Nico Kadel-Garcia'
> > Cc: users@subversion.tigris.org
> > Subject: RE: "OPTIONS request failed" on commit
> >
> >
> >
> > > -----Original Message-----
> > > From: Nico Kadel-Garcia [mailto:nkadel@comcast.net]
> > > Sent: Monday, May 15, 2006 8:38 PM
> > > To: Jeff Jensen
> > > Cc: users@subversion.tigris.org
> > > Subject: Re: "OPTIONS request failed" on commit
> > >
> > > Jeff Jensen wrote:
> > >
> > > > And svn commit -m "Add main dir." gives:
> > > > svn: Commit failed (details follow):
> > > > svn: OPTIONS request failed on '/svn/playground'
> > > > svn: The OPTIONS request returned invalid XML in the
> > response: XML
> > > > parse error at line 1: no element found (/svn/playground)
> > > >
> > > >
> > > > What perms are needed for Apache/web-dav to respond to
> > the OPTIONS
> > > > command? What feature in a firewall could block it?
> > >
> > > OK, the checkout apparently worked. Or did you not do a clean new
> > > checkout?
> >
> > Yes, clean. Was empty workspace & repo - brand new repo for
> > "playground".
> > svn co brought nothing down, but was successful/no errors.
> >
> >
> > > Also, just in case you're running into "locale" related
> > craziness, try
> > > leaving out the "-m" message option?
> >
> > Same result using an editor for the msg.
> >
> >
> > > Also, take a look at the /var/log/httpd logs, or wherever
> > your Apache
> > > puts them.
> >
> > I see no error messages. Suggests it doesn't get to Apache(?).
> >
> >
> > > And take a look at your pre-commit scripts. Do you have one
> > in place?
> > > Is it perhaps doing something odd?
> >
> > None.
> >
> >
> > > Last, do you have some *OTHER* oddness in your httpd.conf
> going on?
> >
> > Great question...how do I know!? :-) It is out-of-the-box with
> > additions for Bugzilla and XPlanner (been running for about 1.5
> > years).
> >
> > Hints for what to look for, what you are thinking of?
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: "OPTIONS request failed" on commit
Posted by Jeff Jensen <je...@upstairstechnology.com>.
Is there something else to do to enable either WebDAV or SVN DAV, other than
what is in the <Location> block? Trying to track down what would disable or
block OPTIONS WebDAV method...
> -----Original Message-----
> From: Jeff Jensen [mailto:jeffjensen@upstairstechnology.com]
> Sent: Monday, May 15, 2006 9:07 PM
> To: 'Nico Kadel-Garcia'
> Cc: users@subversion.tigris.org
> Subject: RE: "OPTIONS request failed" on commit
>
>
>
> > -----Original Message-----
> > From: Nico Kadel-Garcia [mailto:nkadel@comcast.net]
> > Sent: Monday, May 15, 2006 8:38 PM
> > To: Jeff Jensen
> > Cc: users@subversion.tigris.org
> > Subject: Re: "OPTIONS request failed" on commit
> >
> > Jeff Jensen wrote:
> >
> > > And svn commit -m "Add main dir." gives:
> > > svn: Commit failed (details follow):
> > > svn: OPTIONS request failed on '/svn/playground'
> > > svn: The OPTIONS request returned invalid XML in the
> response: XML
> > > parse error at line 1: no element found (/svn/playground)
> > >
> > >
> > > What perms are needed for Apache/web-dav to respond to
> the OPTIONS
> > > command? What feature in a firewall could block it?
> >
> > OK, the checkout apparently worked. Or did you not do a clean new
> > checkout?
>
> Yes, clean. Was empty workspace & repo - brand new repo for
> "playground".
> svn co brought nothing down, but was successful/no errors.
>
>
> > Also, just in case you're running into "locale" related
> craziness, try
> > leaving out the "-m" message option?
>
> Same result using an editor for the msg.
>
>
> > Also, take a look at the /var/log/httpd logs, or wherever
> your Apache
> > puts them.
>
> I see no error messages. Suggests it doesn't get to Apache(?).
>
>
> > And take a look at your pre-commit scripts. Do you have one
> in place?
> > Is it perhaps doing something odd?
>
> None.
>
>
> > Last, do you have some *OTHER* oddness in your httpd.conf going on?
>
> Great question...how do I know!? :-) It is out-of-the-box
> with additions for Bugzilla and XPlanner (been running for
> about 1.5 years).
>
> Hints for what to look for, what you are thinking of?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: "OPTIONS request failed" on commit
Posted by Jeff Jensen <je...@upstairstechnology.com>.
> -----Original Message-----
> From: Nico Kadel-Garcia [mailto:nkadel@comcast.net]
> Sent: Monday, May 15, 2006 8:38 PM
> To: Jeff Jensen
> Cc: users@subversion.tigris.org
> Subject: Re: "OPTIONS request failed" on commit
>
> Jeff Jensen wrote:
>
> > And svn commit -m "Add main dir." gives:
> > svn: Commit failed (details follow):
> > svn: OPTIONS request failed on '/svn/playground'
> > svn: The OPTIONS request returned invalid XML in the response: XML
> > parse error at line 1: no element found (/svn/playground)
> >
> >
> > What perms are needed for Apache/web-dav to respond to the OPTIONS
> > command? What feature in a firewall could block it?
>
> OK, the checkout apparently worked. Or did you not do a clean
> new checkout?
Yes, clean. Was empty workspace & repo - brand new repo for "playground".
svn co brought nothing down, but was successful/no errors.
> Also, just in case you're running into "locale" related
> craziness, try leaving out the "-m" message option?
Same result using an editor for the msg.
> Also, take a look at the /var/log/httpd logs, or wherever
> your Apache puts them.
I see no error messages. Suggests it doesn't get to Apache(?).
> And take a look at your pre-commit scripts. Do you have one
> in place? Is it perhaps doing something odd?
None.
> Last, do you have some *OTHER* oddness in your httpd.conf going on?
Great question...how do I know!? :-) It is out-of-the-box with additions
for Bugzilla and XPlanner (been running for about 1.5 years).
Hints for what to look for, what you are thinking of?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "OPTIONS request failed" on commit
Posted by Nico Kadel-Garcia <nk...@comcast.net>.
Jeff Jensen wrote:
> And svn commit -m "Add main dir." gives:
> svn: Commit failed (details follow):
> svn: OPTIONS request failed on '/svn/playground'
> svn: The OPTIONS request returned invalid XML in the response: XML
> parse error at line 1: no element found (/svn/playground)
>
>
> What perms are needed for Apache/web-dav to respond to the OPTIONS
> command? What feature in a firewall could block it?
OK, the checkout apparently worked. Or did you not do a clean new checkout?
Also, just in case you're running into "locale" related craziness, try
leaving out the "-m" message option?
Also, take a look at the /var/log/httpd logs, or wherever your Apache puts
them.
And take a look at your pre-commit scripts. Do you have one in place? Is it
perhaps doing something odd?
Last, do you have some *OTHER* oddness in your httpd.conf going on?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: "OPTIONS request failed" on commit
Posted by Jeff Jensen <je...@upstairstechnology.com>.
> -----Original Message-----
> From: Nico Kadel-Garcia [mailto:nkadel@comcast.net]
> Sent: Monday, May 15, 2006 6:37 PM
> To: Jeff Jensen
> Cc: users@subversion.tigris.org
> Subject: Re: "OPTIONS request failed" on commit
>
> Jeff Jensen wrote:
> > Quoting Nico Kadel-Garcia <nk...@comcast.net>:
> >
> >> Jeff Jensen wrote:
> >>> Thank you for the reply.
> >>>
> >>> I commented out that line so we have no authorization in place,
> >>> restarted httpd, and the same problem occurs :-(.
> >>>
> >>>
> >>> Quoting Nico Kadel-Garcia <nk...@comcast.net>:
> >>>
> >>>> Jeff Jensen wrote:
> >>>>> Hi,
> >>>>>
> >>>>> We temporarily setup svnserve for our new Subversion
> server (and
> >>>>> it works :-), and now are trying to setup use through
> Apache. We
> >>>>> have it partially working from remote (e.g. authentication,
> >>>>> authorization, svn co, browser traversing), but cannot commit.
> >>>>>
> >>>>> Using:
> >>>>> svn, version 1.1.4 (r13838)
> >>>>> compiled Apr 5 2005, 05:18:28
> >>>>>
> >>>>> Apache/2.0.53
> >>>>>
> >>>>>
> >>>>> We've been pulling our hair out Googling and searching
> this list's
> >>>>> archives etc. (every thread starts to answer something,
> but then
> >>>>> ends :-( I know there is some config error on our
> part. So far
> >>>>> we have not determined what it is!
> >>>>>
> >>>>> Our best guess so far is there is/are another thing to
> config in
> >>>>> httpd.conf, or something with our firewall/forwarding. For
> >>>>> starters, we understand that the web-dav OPTIONS command is not
> >>>>> working, but not sure how to get further/troubleshoot
> and diagnose
> >>>>> why.
> >>>>>
> >>>>> The core issue to solve is this error:
> >>>>>
> >>>>> $ svn commit -m "the msg"
> >>>>> svn: Commit failed (details follow):
> >>>>> svn: OPTIONS request failed on '/svn/mndoc'
> >>>>> svn: The OPTIONS request returned invalid XML in the
> response: XML
> >>>>> parse error at line 1: no element found (/svn/mndoc)
> >>
> >> Hmm. So svnserve works, and you've got a repository at /svn/mndoc?
> >> What does a web browser show as present there?
> >
> > Yes, yes. Browser shows the dirs (e.g. tags, branches)! Clicking
> > into them works. This is confusing for us because it
> partially works.
>
> What does "svn status" say? Which files or directories are
> you *expecting* to change, and what happens if you change
> them one at a time?
Executing svn status shows exactly what I would expect.
It doesn't matter if I have 1 file/dir to add or many; the result is the
same: the problem.
I created a new "playground" repo, and I can't even add a top level dir.
The same problem occurs. For example, I did:
svn mkdir main
svn status shows:
A main
And svn commit -m "Add main dir." gives:
svn: Commit failed (details follow):
svn: OPTIONS request failed on '/svn/playground'
svn: The OPTIONS request returned invalid XML in the response: XML parse
error at line 1: no element found (/svn/playground)
What perms are needed for Apache/web-dav to respond to the OPTIONS command?
What feature in a firewall could block it?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "OPTIONS request failed" on commit
Posted by Nico Kadel-Garcia <nk...@comcast.net>.
Jeff Jensen wrote:
> Quoting Nico Kadel-Garcia <nk...@comcast.net>:
>
>> Jeff Jensen wrote:
>>> Thank you for the reply.
>>>
>>> I commented out that line so we have no authorization in place,
>>> restarted httpd, and the same problem occurs :-(.
>>>
>>>
>>> Quoting Nico Kadel-Garcia <nk...@comcast.net>:
>>>
>>>> Jeff Jensen wrote:
>>>>> Hi,
>>>>>
>>>>> We temporarily setup svnserve for our new Subversion server (and
>>>>> it works :-), and now are trying to setup use through Apache. We
>>>>> have it partially working from remote (e.g. authentication,
>>>>> authorization, svn co, browser traversing), but cannot commit.
>>>>>
>>>>> Using:
>>>>> svn, version 1.1.4 (r13838)
>>>>> compiled Apr 5 2005, 05:18:28
>>>>>
>>>>> Apache/2.0.53
>>>>>
>>>>>
>>>>> We've been pulling our hair out Googling and searching this list's
>>>>> archives etc. (every thread starts to answer something, but then
>>>>> ends :-( I know there is some config error on our part. So far
>>>>> we have not determined what it is!
>>>>>
>>>>> Our best guess so far is there is/are another thing to config in
>>>>> httpd.conf, or something with our firewall/forwarding. For
>>>>> starters, we understand that the web-dav OPTIONS command is not
>>>>> working, but not sure how to get further/troubleshoot and diagnose
>>>>> why.
>>>>>
>>>>> The core issue to solve is this error:
>>>>>
>>>>> $ svn commit -m "the msg"
>>>>> svn: Commit failed (details follow):
>>>>> svn: OPTIONS request failed on '/svn/mndoc'
>>>>> svn: The OPTIONS request returned invalid XML in the response: XML
>>>>> parse error at line 1: no element found (/svn/mndoc)
>>
>> Hmm. So svnserve works, and you've got a repository at /svn/mndoc?
>> What does a web browser show as present there?
>
> Yes, yes. Browser shows the dirs (e.g. tags, branches)! Clicking
> into them works. This is confusing for us because it partially works.
What does "svn status" say? Which files or directories are you *expecting*
to change, and what happens if you change them one at a time?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "OPTIONS request failed" on commit
Posted by Jeff Jensen <je...@upstairstechnology.com>.
Quoting Nico Kadel-Garcia <nk...@comcast.net>:
> Jeff Jensen wrote:
> > Thank you for the reply.
> >
> > I commented out that line so we have no authorization in place,
> > restarted httpd, and the same problem occurs :-(.
> >
> >
> > Quoting Nico Kadel-Garcia <nk...@comcast.net>:
> >
> >> Jeff Jensen wrote:
> >>> Hi,
> >>>
> >>> We temporarily setup svnserve for our new Subversion server (and it
> >>> works :-), and now are trying to setup use through Apache. We have
> >>> it partially working from remote (e.g. authentication,
> >>> authorization, svn co, browser traversing), but cannot commit.
> >>>
> >>> Using:
> >>> svn, version 1.1.4 (r13838)
> >>> compiled Apr 5 2005, 05:18:28
> >>>
> >>> Apache/2.0.53
> >>>
> >>>
> >>> We've been pulling our hair out Googling and searching this list's
> >>> archives etc. (every thread starts to answer something, but then
> >>> ends :-( I know there is some config error on our part. So far we
> >>> have not determined what it is!
> >>>
> >>> Our best guess so far is there is/are another thing to config in
> >>> httpd.conf, or something with our firewall/forwarding. For
> >>> starters, we understand that the web-dav OPTIONS command is not
> >>> working, but not sure how to get further/troubleshoot and diagnose
> >>> why.
> >>>
> >>> The core issue to solve is this error:
> >>>
> >>> $ svn commit -m "the msg"
> >>> svn: Commit failed (details follow):
> >>> svn: OPTIONS request failed on '/svn/mndoc'
> >>> svn: The OPTIONS request returned invalid XML in the response: XML
> >>> parse error at line 1: no element found (/svn/mndoc)
>
> Hmm. So svnserve works, and you've got a repository at /svn/mndoc? What does
> a web browser show as present there?
Yes, yes. Browser shows the dirs (e.g. tags, branches)! Clicking into them
works. This is confusing for us because it partially works.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "OPTIONS request failed" on commit
Posted by Nico Kadel-Garcia <nk...@comcast.net>.
Jeff Jensen wrote:
> Thank you for the reply.
>
> I commented out that line so we have no authorization in place,
> restarted httpd, and the same problem occurs :-(.
>
>
> Quoting Nico Kadel-Garcia <nk...@comcast.net>:
>
>> Jeff Jensen wrote:
>>> Hi,
>>>
>>> We temporarily setup svnserve for our new Subversion server (and it
>>> works :-), and now are trying to setup use through Apache. We have
>>> it partially working from remote (e.g. authentication,
>>> authorization, svn co, browser traversing), but cannot commit.
>>>
>>> Using:
>>> svn, version 1.1.4 (r13838)
>>> compiled Apr 5 2005, 05:18:28
>>>
>>> Apache/2.0.53
>>>
>>>
>>> We've been pulling our hair out Googling and searching this list's
>>> archives etc. (every thread starts to answer something, but then
>>> ends :-( I know there is some config error on our part. So far we
>>> have not determined what it is!
>>>
>>> Our best guess so far is there is/are another thing to config in
>>> httpd.conf, or something with our firewall/forwarding. For
>>> starters, we understand that the web-dav OPTIONS command is not
>>> working, but not sure how to get further/troubleshoot and diagnose
>>> why.
>>>
>>> The core issue to solve is this error:
>>>
>>> $ svn commit -m "the msg"
>>> svn: Commit failed (details follow):
>>> svn: OPTIONS request failed on '/svn/mndoc'
>>> svn: The OPTIONS request returned invalid XML in the response: XML
>>> parse error at line 1: no element found (/svn/mndoc)
Hmm. So svnserve works, and you've got a repository at /svn/mndoc? What does
a web browser show as present there?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "OPTIONS request failed" on commit
Posted by Jeff Jensen <je...@upstairstechnology.com>.
Thank you for the reply.
I commented out that line so we have no authorization in place, restarted httpd,
and the same problem occurs :-(.
Quoting Nico Kadel-Garcia <nk...@comcast.net>:
> Jeff Jensen wrote:
> > Hi,
> >
> > We temporarily setup svnserve for our new Subversion server (and it
> > works :-), and now are trying to setup use through Apache. We have
> > it partially working from remote (e.g. authentication, authorization,
> > svn co, browser traversing), but cannot commit.
> >
> > Using:
> > svn, version 1.1.4 (r13838)
> > compiled Apr 5 2005, 05:18:28
> >
> > Apache/2.0.53
> >
> >
> > We've been pulling our hair out Googling and searching this list's
> > archives etc. (every thread starts to answer something, but then ends
> > :-( I know there is some config error on our part. So far we have
> > not determined what it is!
> >
> > Our best guess so far is there is/are another thing to config in
> > httpd.conf, or something with our firewall/forwarding. For starters,
> > we understand that the web-dav OPTIONS command is not working, but
> > not sure how to get further/troubleshoot and diagnose why.
> >
> > The core issue to solve is this error:
> >
> > $ svn commit -m "the msg"
> > svn: Commit failed (details follow):
> > svn: OPTIONS request failed on '/svn/mndoc'
> > svn: The OPTIONS request returned invalid XML in the response: XML
> > parse error at line 1: no element found (/svn/mndoc)
> >
> >
> > This is the section added to http.conf
> > <IfModule mod_dav_svn.c>
> > <Location /svn>
> > DAV svn
> > SVNParentPath /home/subversion/repos
> >
> > #access control policy
> > AuthzSVNAccessFile /home/subversion/conf/authorization-apache
>
> I suggest that this is a big part of your problem. The SVNAccess format
> is.... odd. Take a look at the svnperms.py and svnperms.conf files for using
> a pre-commit hook script to control access.
>
> > #how to authenticate
> > AuthType Basic
> > AuthName "Subversion Repository"
> > AuthUserFile /home/subversion/conf/authentication-apache
> >
> > #only authenticated users can access
> > Require valid-user
> > </Location>
> > </IfModule>
> >
> > Anyone have advice for us please?!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "OPTIONS request failed" on commit
Posted by Nico Kadel-Garcia <nk...@comcast.net>.
Jeff Jensen wrote:
> Hi,
>
> We temporarily setup svnserve for our new Subversion server (and it
> works :-), and now are trying to setup use through Apache. We have
> it partially working from remote (e.g. authentication, authorization,
> svn co, browser traversing), but cannot commit.
>
> Using:
> svn, version 1.1.4 (r13838)
> compiled Apr 5 2005, 05:18:28
>
> Apache/2.0.53
>
>
> We've been pulling our hair out Googling and searching this list's
> archives etc. (every thread starts to answer something, but then ends
> :-( I know there is some config error on our part. So far we have
> not determined what it is!
>
> Our best guess so far is there is/are another thing to config in
> httpd.conf, or something with our firewall/forwarding. For starters,
> we understand that the web-dav OPTIONS command is not working, but
> not sure how to get further/troubleshoot and diagnose why.
>
> The core issue to solve is this error:
>
> $ svn commit -m "the msg"
> svn: Commit failed (details follow):
> svn: OPTIONS request failed on '/svn/mndoc'
> svn: The OPTIONS request returned invalid XML in the response: XML
> parse error at line 1: no element found (/svn/mndoc)
>
>
> This is the section added to http.conf
> <IfModule mod_dav_svn.c>
> <Location /svn>
> DAV svn
> SVNParentPath /home/subversion/repos
>
> #access control policy
> AuthzSVNAccessFile /home/subversion/conf/authorization-apache
I suggest that this is a big part of your problem. The SVNAccess format
is.... odd. Take a look at the svnperms.py and svnperms.conf files for using
a pre-commit hook script to control access.
> #how to authenticate
> AuthType Basic
> AuthName "Subversion Repository"
> AuthUserFile /home/subversion/conf/authentication-apache
>
> #only authenticated users can access
> Require valid-user
> </Location>
> </IfModule>
>
> Anyone have advice for us please?!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org