[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn+ssh vs. https (different access methods)

From: <d.guthmann_at_gmx.net>
Date: Wed, 15 Feb 2012 12:31:39 +0100


-------- Original-Nachricht --------

> What kind of trouble did you have with apache in the reverse-proxy
> mode? I've had that working and I think the only issue was that the
> relative path had to be the same as the actual target. That is you
> can't proxy http:/realhost/svn as http://proxyhost/somewhere/svn.
> Also for a straight passthrough you might run stunnel accepting https
> from outside your dmz, connecting to http on the inside server.

I had a problem using the COPY-Command over the connections established over the reverse-proxy...
"Server sent unexpected return value (502 Bad Gateway) in response to COPY request for ..."

But today I've found out that there is a solution using Apache 2.2.4 or greater (add "RequestHeader edit Destination ^https http early" to the Subversion-Configuration):


Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Received on 2012-02-15 12:32:14 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.