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

Re: BUDDY: svn copy https-to-https gives "502 bad gateway"?

From: Jay Levitt <lists-svn_at_shopwatch.org>
Date: 2005-10-21 19:52:16 CEST

kfogel@collab.net wrote:

>Jay Levitt <lists-svn@shopwatch.org> writes:
>
>
>>I've seen this pop up several times around the net, without any
>>resolution, so I expect it's a bug that just hasn't been logged in the
>>issue tracker. But I'm being a good boy and using the buddy system...
>>
>>
>
>Thanks :-).
>
>I like the innovation of using the "BUDDY" keyword on the subject
>line, and will keep an eye out for that in the future.
>
>
>
>>I have a simple Apache-2.0.54-based subversion repository. I've
>>restricted it to https only. It uses a VirtualHost domain, and sits
>>in the root directory of that VirtualHost. (I wouldn't be surprised
>>if this is part of the failcase.)
>>
>>I can svn add, delete, and checkout with no problem. But when I went
>>to create my first tag:
>>
>>svn copy https://svn.example.com/sysadmin/trunk
>>https://svn.example.com/sysadmin/tags/nearly-stock -m "Creating
>>nearly-stock tag"
>>
>>I got a "502 Bad Gateway" error. Apache error log shows nothing but
>>the usual trouble finding "error" files. Apache access log shows:
>>
>>
For the archive's sake: I did not file a bug on this, because when I
went back to debug it, my fail case no longer failed. Unfortunately and
ironically, it disappeared in the process of getting httpd.conf into
svn, so I have no idea what changed... if anybody ever sees this again,
and is interested enough to let me debug on their machine, I'll volunteer.
Received on Fri Oct 21 19:55:20 2005

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

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