[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: "OPTIONS request failed" on commit

From: Jeff Jensen <jeffjensen_at_upstairstechnology.com>
Date: 2006-05-16 04:06:56 CEST


> -----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?


> 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
Received on Tue May 16 04:08:03 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.