Hello Srikanth,
I suppose you've seen these:
- http://svn.haxx.se/users/archive-2006-03/0549.shtml
- http://svn.haxx.se/users/archive-2003-08/0780.shtml
Actually, it seems there is no standard solution. Greg Stein has refused
to implement a workaround in the Apache module: the problem happens
because the hardware (reverse proxy, SSL accelerator or whatever
decrypts the HTTPS) doesn't do correctly his job. It modifies the URL in
the request but not in the "Destination" header of the DAV "COPY"
requests (these DAV requests are issued from SVN when you do either a
"copy" or "move"). Then when svn checks the parameters, it finds
something incorrect. The position of Greg is understandable as it's not
a problem caused by Apache or by SVN.
The way we've fixed it here has required implementing a script inside
the ssl accelerator, in order to also modify the "Destination" header in
the DAV "COPY" requests to our SVN server. This solution works perfect,
we've almost forgotten it's in place. If you can't do it in your reverse
proxy, it's also possible to do it with a PERL script installed inside
Apache (using mod_perl and the directives SetHandler and
PerlHeaderParserHandler in the apache configuration file). If both these
can't be done in your environment, your last resort will be the solution
you suggested: activate the ssl connection between the reverse proxy and
Apache (but this wasn't possible here). I hope this helps.
Best Regards,
Jean-Pol Landrain.
Note: I cc to the SVN mailing list as I see this question comes often
and other people might be interested too. Well, what about adding it to
the SVN FAQ ???
-----Original Message-----
From: Srikanth [mailto:srikanth.minnam@qvantel.com]
Sent: 18 February 2007 11:00
To: Hermann Maurer; LANDRAIN Jean-Pol
Subject: svn COPY 502 bad gateway over HTTPS
Hello Hermann & Jean-Pol
We are stuck with the problem that 'svn COPY 502 bad
gateway over HTTPS'
I just browsed through the SVN forums and you guys had
a solution for 'svn COPY 502 bad gateway over HTTPS'
problem.
We have an external apache running HTTPS and internal
server running HTTP.
Is it so that the solution is to make ssl connection
between the reverse proxy and the internal apache
server?
Any help will be greatly appreciated.
rgds
Srikanth Minnam
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 19 14:20:46 2007