List Info

Thread: Commit fails on proxied Subversion




Commit fails on proxied Subversion
user name
2006-05-23 07:41:51
Hi All,

I've read and reread all I could find on using mod_proxy to
proxy
Subversion requests to Apache. Apparently, commits don't
seem to be
working for me:

svn: Commit failed (details follow):
svn: OPTIONS request failed on '/svn/xyz/trunk'
svn: OPTIONS of '/svn/xyz/trunk': 200 OK (https://localhost:1234)

1234 is a Lighttpd port and everything else works: FastCGI,
authentication, SSL. Apache listens on port 1235, and the
relative URI
for this repository is exactly the same on both Web servers:
/svn/xyz.
If I use direct Apache URL (essentially, use the same URL
but substitute
"http" instead of "https" and port
1235), everything works. If I use
Lighttpd URL (https, port 1234), checkout and update work,
commit does
not. It appears that I am up against a problem with OPTIONS
proxying
mentioned here: http://article.gmane.org/gmane.comp.web.lighttpd/2313,
which I thought was resolved in version 1.4.11 (and
documented as a
recipe here http://trac.lighttpd.net/trac/wiki/ApacheSubversionReci
pe).
This OPTIONS request doesn't appear to reach Apache.
Details follow. It's Lighttpd 1.4.11 on Ubuntu 6 (Dapper),
Apache 2.0.55
and Subversion 1.3.1. SSL and authentication (htdigest) are
enabled only
on Lighttpd, which listens on all interfaces. Apache listens
only on
local interface. SSL uses a self-signed certificate that is
permanently
accepted by svn client. The error happens whether I go via
localhost or
external IP address. I would be grateful for any pointers.

Thank you,
Sergey.

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )