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

[Subclipse-users] 502 Bad Gateway via SSL / Sourceforge - Fixed

From: Brice Burgess <bhb_at_iceburg.net>
Date: 2006-05-06 03:55:34 CEST

I was having severe issues integrating Subclipse with SourceForge.Net's
SVN service (offered via HTTPS / Port 443 SSL). I'd get errors like:

copy -rHEAD https://svn.sourceforge.net/svnroot/pommo/aardvark 
svn: Commit failed (details follow):
svn: COPY of /svnroot/pommo/!svn/bc/4/aardvark: 502 Bad Gateway 
Whenever executing a COPY command.
It appears that the cause is in JavaSVN. Subclipse can be configured to 
use either the JavaSVN or JavaHL libraries for its SVN API (via 
Preferences->Team->SVN). By default, JavaHL will be used if it is 
installed on the system. JavaHL is officially supported and updated by 
the Subversion project. If Subclipse cannot find the JavaHL library, it 
will roll back to JavaSVN -- a 100% pure JAVA version of SVN's API.
There is a bug in JavaSVN with SSL apparently. This caused the bad 
gateway. Either this bug needs to be patched, or you need to switch to 
JavaHL (like I did).
To switch to JavaHL -- see the FAQ @ Subclipse project: 
If you compile from scratch.. one cadveat --> the FAQ lists that you 
want to flag --enable-ssl. This will NOT work. You must pass --with-ssl 
to compile SSL support. The FAQ should be updated to reflect this? :)
I hope this helps,
~ Brice Burgess
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sat May 6 03:53:26 2006

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

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