> -----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 <nkadel@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 <nkadel@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
Received on Tue May 16 02:26:49 2006