This problem is also described in chapter 6 of the online
svnbook.red-bean.com, in a big tan box:
http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.basic
On 7/20/07, Freek Dijkstra <public@macfreek.nl> wrote:
> Here is a problem with solution. Perhaps someone searching the archives
> may benefit from it.
>
> But mostly, it's just a short "holy cow, software can get really hairy"
> story I want to share with you. Just in case you thought that the
> "restricted folder underneath public root" was complex. Hah.
>
> Problem: svn move does not work. After a svn move, a commit results in
> the error:
> svn: Commit failed (details follow):
> svn: COPY of newname.txt: 502 Bad Gateway (https://svn.example.org)
>
> No, we do not *have* a reverse HTTP proxy, in case you was going to
> suggest that as possible cause.
>
> Solution:
> Copy the "SSLEngine on" directive to another location in the Apache
> configuration.
>
> "Huh?" You may ask. If you like to know why, the details are at
> http://www.science.uva.nl/research/air/wiki/Subversion502BadGateway
>
> I'd say this is another nice example of Leaky abstractions [1].
>
> Now my head hurts. Have a nice day. :-)
>
> Freek
>
> [1] http://www.joelonsoftware.com/articles/LeakyAbstractions.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 20 14:36:54 2007