COPY causes 502 Bad Gateway through reverse proxy

Hello,

I have a setup where my subversion repository is hosted on a
local/private network and if someone is *outside* this network they can
make requests to the public reverse proxy.

Both servers (subversion server and reverse proxy) are apache 2.0.53.
Connections to the reverse proxy are https. The connection to the
internal subversion server is regular http. Authentication is basic
auth and is handled by the internal subversion server.

In fact, this whole setup looks a lot like the setup described in this
e-mail that was previously sent to this list:

http://svn.haxx.se/users/archive-2005-03/0531.shtml

I also have the same problem as the author of that e-mail. Basically,
when I commit changes that will involve a DAV COPY, they fail with a Bad
Gateway error. Everything else appears to work. In fact, I've been
using this setup for quite some time (around 2 years) and have never
noticed this problem. Maybe I haven't done too many moves or copies or
perhaps it is an error introduced recently by either myself or apache or
subversion ...

The relevant log lines from the reverse proxy and from the subversion
server are located here:

http://sethd.org/wiki/SubversionProxyErrors

The subversion commands used to generate the above sequence were:

svn move wcfile newwcfile
svn commit

The relevant lines in the reverse proxy's configuration file:

<VirtualHost *:443>
  ServerName dev.xxxxxx.com
  Options none

  # proxy to subversion
  ProxyRequests off
  ProxyPass / http://dev.xxxxxx.com/
  ProxyPassReverse / http://dev.xxxxxx.com/
</VirtualHost>

Thanks for any help.

-- 
seth / @sethdaniel.org
When I was little, I went into a pet shop and they asked how big I'd get.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org