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
Received on Wed May 17 06:04:19 2006