Re: OPTIONS request failed error

Shay Harding wrote:
> On Tue, 2002-08-13 at 15:41, Julian Fitzell wrote:
>
>>Shay Harding wrote:
>>
>>>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
>>></Location>
>>
>> >
>>
>>Perhaps I'm missing something but why is that Alias directive there?
>>Looks to me like you've got two thing serving the same URL path
>>("/alias") though I have no idea which take precedence. I also don't
>>quite see how that would cause a 301 but I always try to remove the
>>extraneous stuff first and see if the problem is still there. If
>>there's actually a reason for that Alias, my mistake...
>>
>>[...]
>>
>>>
>>>Any help or insight would surely be appreciated.
>>
>>Julian
>
>
> The 'Alias' exists because '/repos' is not in the DocumentRoot so Apache
> needs to know where to find it or else it will return a 404.
>

Have you tried it without the Alias?

 From the apache docs about Location:

"Note that URLs do not have to line up with the filesystem at all, it
should be emphasized that <Location> operates completely outside the
filesystem."

The only thing that knows the filepath is the mod_dav_svn (from the
SVNPath directive).

Your success from adding a / may be just that the Location is then
matching and the Alias is not.

I certainly don't have an Alias and it works fine.

Julian

-- 
julian@beta4.com
Beta4 Productions (http://www.beta4.com)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org