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

Software complexity (502 Bad Gateway)

From: Freek Dijkstra <public_at_macfreek.nl>
Date: 2007-07-20 09:06:01 CEST

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.

Copy the "SSLEngine on" directive to another location in the Apache

"Huh?" You may ask. If you like to know why, the details are at

I'd say this is another nice example of Leaky abstractions [1].

Now my head hurts. Have a nice day. :-)


[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
Received on Fri Jul 20 09:05:14 2007

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.