Comments on: Subversion – ’502 Bad Gateway’ Workaround

By: Carles Barrobés

Carles Barrobés — Mon, 05 Oct 2009 09:34:49 +0000

I’ve found a quite good explanation, plus a simpler solution to this problem:
http://svn.haxx.se/users/archive-2006-03/0549.shtml

Also described in Apache documentation of mod_headers.
http://publib.boulder.ibm.com/httpserv/manual70/mod/mod_headers.html

My setup is the following: I have a default SSL configuration, plus some name virtual hosts under directives, as seems to be your case.

The steps needed for me were just:

1. Activate mod_headers

2. Add the following entry inside my directive:
RequestHeader edit Destination ^https: http: early

This way I do not need to replicate the SSL directives from my default SSL virtual host file.

By: gabriel

gabriel — Mon, 06 Jul 2009 18:48:58 +0000

great! thank you!

By: Tor Håkon Haugen

Tor Håkon Haugen — Fri, 05 Jun 2009 19:05:59 +0000

Mads: If you try, please let me know. I’m currently not running SVN, but it would be nice to be able to update this post since people still is reading it and finding it useful.

By: John

John — Fri, 05 Jun 2009 15:53:50 +0000

Cool, it helped !

Still have to see if the 3 last lines are needed…

By: Solution for Subversion 502 Bad Gateway problem when using Forefront as reverse proxy - Mads Nissen

Sun, 28 Dec 2008 14:50:56 +0000

[...] Christian Stocker suggests using a perl script to solve this problem, and Tor Håkon Haugen adds some more SSL config, but there is a much simpler solution available if your setup is much like mine. Just add this line [...]

By: Greg

Greg — Tue, 16 Sep 2008 05:27:49 +0000

Thanks. This tip solved my problem.

Cheers

By: david

david — Tue, 23 Oct 2007 13:34:48 +0000

way cool. at last a solution to my trauma of years.

THANKS

By: matthew

matthew — Sun, 02 Sep 2007 13:05:04 +0000

Thank you!

I had recently moved my SVN installation into a separate vhost from my main SSL host and was wondering what the hell was going on.

By: yankeehoo

yankeehoo — Thu, 16 Aug 2007 16:18:24 +0000

I was battling the same 502 error for years. It turns out all I needed to add to my apache configuration was the SSLEngine On directive…