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

502 Bad gateway in https-http proxy setup

From: Ivo van der Wijk <vladdrac_at_gmail.com>
Date: 2004-08-10 23:49:22 CEST


It seems subversion (or perhaps some apache / dav component?) gets
confused if a https destination header is passed through a standard
http channel. Apache responds with a "502 Bad Gateway" in such cases
when a COPY operation is performed.

This is what occured when we attempted to mod_proxy our internal http
svn repository externally through https -- i.e.

https -> gateway + mod_proxy -> internal http server

I've currently fixed this problem by inserting a small rewriting proxy
in between that fixes the destination header. Details can be found at

Should this be considered a bug? Or just an impossible configuration?



Drs. I.R. van der Wijk                                      -=-
Korte Leidsedwarsstraat 12                                 Amaze
1017 RC Amsterdam, NL                                       -=-
T +31-20-4688336         F +31-20-4688337       Zope/Plone/Content Management
W http://www.amaze.nl    E info_at_amaze.nl           Open Source Solutions
W http://vanderwijk.info E ivo_at_amaze.nl                 Consultancy
PGP http://vanderwijk.info/pgp
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 11 00:04:21 2004

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

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