Trying to get SwiftMailer into sf.net's SVN repository. Everything works fine except for the usual issue I always get with using SSL connections with subversion. Look at this:
[d11wtq@pc-cac swiftmailer]$ svn copy trunk/php5 tags/php5/2.1.17
A tags/php5/2.1.17
[d11wtq@pc-cac swiftmailer]$ svn copy trunk/php4 tags/php4/2.1.17
A tags/php4/2.1.17
[d11wtq@pc-cac swiftmailer]$ svn commit tags -m "Taking clean snapshot at 2.1.17"
Adding tags/php4/2.1.17
svn: Commit failed (details follow):
svn: COPY of php4/2.1.17: 502 Bad Gateway (https://swiftmailer.svn.sf.net)
[d11wtq@pc-cac swiftmailer]$ svn commit tags/php5 -m "Taking clean snapshot at 2.1.17"
Adding tags/php5/2.1.17
svn: Commit failed (details follow):
svn: COPY of 2.1.17: 502 Bad Gateway (https://swiftmailer.svn.sf.net)
[d11wtq@pc-cac swiftmailer]$
Am I really doing something wrong? I have never once got "copy" to work with SSL and I find it hard to belive SF.net would use SSL if it didn't work. BUT I have read elsewhere the svn copy doesn't work with SSL since the instructions for dav are turned into normal unecrypted requests and something breaks along the way.
I don't get it. Half a day's worth of Googling and loads of people have the same problem. Everything suggests the issue is at the server and not the client. SF have provided SVN access for ages now so I doubt they're still fixing issues considering they've even gone to the extent of creating tools tools to convert your CVS based project into SVN.
The weird thing is that this has happened to me on every linux box I have used SVN from and not just on SF's servers; but only when going over SSL.
I trawled through the SF support tracker and found a fair few people also complaining about this only to be responded to by the usual automated bot. Very frustrating
EDIT | I discovered that you don't need SSL like they say you do on their guide. It works with just http too and voila! It's working fine now
The URI I use for SF when exporting/checking out from a project with HTTPS. Not sure if this is what they set in the docs (I rarely read them) but it definitely works to date. Chances are the SSL is being rejected because of the constantly varying domain from your format...?
Oh gimme strength Turns out they switched the SSL hack for DAV to now use the project subdomain rather than the root svn subdomain. Before it *only* worked on the root svn subdomain.