svn COPY 502 bad gateway over HTTPS

[LANDRAIN Jean-Pol <jp...@europarl.eu.int>]

Hello,
 
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 kind.
 
Best Regards,
Jean-Pol.