“502 Bad Proxy” with subversion and an SSL proxy

  • Christian Stocker

We switched recently to SSL for our Subversion server (announcement on the devblog). Worked fine until I wanted to “svn move” a file. “502 Bad Proxy” was the answer. Some googling around brought me to the root of the problem ( Read this for details) and different solutions, from patching mod_dav (urks), to adding an additional proxy written in either Python or Ruby (double urks) to a nice little mod_perl2 script (just a little bit urks :) ), which is registered as handler in Apache2 and rewrites the culprit “Destination” header. Here's the script and explanation for this. Works as expected :)


Tell us what you think