Theoretically, the solution would be for Apache to SSL-decrypt the
request before applying the proxy rules. I don't know enough about
Apache or mod_ssl to understand why this wasn't implemented this way
from the outset.
From: LANDRAIN Jean-Pol [mailto:firstname.lastname@example.org]
Sent: Monday, March 13, 2006 8:30 AM
Subject: RE: svn COPY 502 bad gateway over HTTPS
I've found an old discussion about this issue:
I have done some tests with one of our network admins and it is exactly
the situation we have here.
As SVN is being adopted by more and more companies, the problem will
come out more and more often. I understand this is not a problem of SVN
or the Apache DAV module, but 3 years later maybe it's time to find a
solution, even if you don't like it. Isn't it ?
From: LANDRAIN Jean-Pol
Sent: 13 March 2006 12:06
Subject: svn COPY 502 bad gateway over HTTPS
My company is using SVN for a few months on a pilot project
(we've been using CVS before and would like to migrate to SVN, but we
must be sure this can be done smoothly). We have now decided to use it
over HTTPs to open it to our external developers. Unfortunately, we're
blocked on a weird (but known) problem: the "svn COPY 502 bad gateway
over HTTPS" problem.
Searching on google and in the svn mailing lists, I've seen
different explanations and solutions (or workarounds) for it, but I
can't decide which one is the correct one and will work for us. We'd
like to find an easy solution, but it doesn't look like this exists.
We're a bit lost with the amount of (often unclear for the novice)
information. If someone could explain us clearly what is the problem (it
looks like it is the mod_dav module in Apache that uses absolute urls
instead of relative ones. Right ? Is it a problem only when using a
reverse proxy over https ?) and how to fix it, that would be really
Received on Mon Mar 13 15:17:13 2006