[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 error

From: Shay Harding <sharding_at_ccbill.com>
Date: 2002-08-14 00:15:14 CEST

On Tue, 2002-08-13 at 08:57, Karl Fogel wrote:
> Shay Harding <sharding@ccbill.com> writes:
> > Ok, I am at my wits end about these problems that suddenly appeared
> > after upgrading to the newest Subversion (revision 2959) and Apache
> > (from CVS).
> >
> > I keep getting the following error no matter what commands I issue:
> >
> > [shayh]# svn mkdir http://localhost/repos/programmers -m "Test"
> > subversion/libsvn_ra_dav/util.c:332: (apr_err=20014, src_err=0)
> > svn: Error string not specified yet
> > svn: OPTIONS request failed on /repos
> > subversion/libsvn_ra_dav/util.c:306: (apr_err=20014, src_err=0)
> > svn: The OPTIONS status was 301, but expected 200.
> >
> > Now this was working before I updated. I get the same error if I try to
> > import anything now as well.
> >
> > Nothing at all appears in the Apache error log, just the above error
> > that gets printed to screen.
> Can you do an ethereal capture of the traffic on port 80?
> (And if you're really feeling ambitious, do the same thing with the
> old code, the version that worked, so we can compare them...)

Well, after messing with this for a while, it seems Apache (or some
component of Apache) is sending back a 301 status (permanent redirect)
for any access to http://localhost/repos where my repository resides. If
I lynx to the page, I get there no problem but that's only because Lynx
redirects me without complaints. If I use 'svn mkdir
http://localhost/repos/A', it errors out because it is expecting a 200
(OK) status, but receiving a 301 status back (guess there's no redirect
capability within mod_dav_svn (or maybe it's the mod_dav) module?

Now as to why the Apache server is insisting on a 301 status... I have
no clue. There are no <Redirect> type tags in the conf file and the SVN
config is:

Alias /repos /var/securewww/repos

<Location /repos>
    DAV svn
    SVNPath /var/securewww/repos

    AllowOverride None
    Options None

same as it was before I upgraded the Apache/SVN/Neon programs. If I
change the config to include a trailing '/', I can get to
http://localhost/repos/ with no 301 occurring as I would expect. Problem
is SVN doesn't like that. That then gives me:

svn_error: #21102 : <RA layer didn't receive requested OPTIONS info>
  The OPTIONS response did not include the requested
(Check the URL again; this often means that the URL is not

Request Header:

    OPTIONS /repos HTTP/1.1\r\n
    User-Agent: neon/0.21.2 SVN/0.14.0 (dev build)\r\n

I'm guessing the above occurs because SVN strips the URL down to
"http://localhost/repos" (as seen in the headers) and now Apache has no
clue where to find this since mod_alias matches the trailing '/'.

It's hard to tell which component is doing what since there's SVN, Neon,
DAV, Apache +(modules, hooks, filters, etc).

The response headers for the above were:

    HTTP/1.1 200 OK\r\n
    Date: Mon, 12 Aug 2002 22:09:34 GMT\r\n
    Server: Apache/2.0.41-dev (Unix) mod_ssl/2.0.41-dev OpenSSL/0.9.6g
DAV/2 SVN/0.14.1 (dev build)\r\n
    Content-Length: 0\r\n
    Keep-Alive: timeout=15, max=100\r\n
    Connection: Keep-Alive\r\n
    Content-Type: text/plain; charset=ISO-8859-1\r\n

Any help or insight would surely be appreciated.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 14 00:11:44 2002

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

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