Unfortunately, it (SSL) is actually necessary in my case (at least while I'm at work)... Most corporate web proxies don't proxy all the HTTP methods required to make WebDAV work. This is denoted in the form of an Error 500.
([EMAIL PROTECTED] ~) svk sync /macports/mirror Syncing https://svn.macports.org/repository/macports Retrieving log information from 25914 to 25914 Committed revision 25947 from revision 25914. ([EMAIL PROTECTED] ~) svk mirror -l | grep macports /macports/mirror https://svn.macports.org/repository/macports ([EMAIL PROTECTED] ~) svk mirror --relocate /macports/mirror http://svn.macports.org/repository/macports Mirror relocated. ([EMAIL PROTECTED] /Code/MacPorts) svk sync /macports/mirror Syncing http://svn.macports.org/repository/macports Retrieving log information from 25915 to 25916 RA layer request failed: REPORT request failed on '/repository/macports/!svn/bc/25916': REPORT of '/repository/macports/!svn/bc/25916': 500 Server Error (http://svn.macports.org) -Mark On 6/5/2007, "Kevin Van Vechten" <[EMAIL PROTECTED]> wrote: >It's not necessary to use SSL to access the repository (we use digest >authentication), and using the plain http:// URL will probably be >more robust. > >- Kevin > >On Jun 5, 2007, at 8:57 AM, Ryan Schmidt wrote: > >> Transmitting file data ........................svn: Commit failed >> (details follow): >> svn: PUT of '/repository/macports/!svn/wrk/55dfb2b4-ae74-47ff-b412- >> db15fdc83ddd/trunk/dports/sysutils/cronolog/Portfile': SSL >> negotiation failed: SSL error: sslv3 alert bad record mac (https:// >> svn.macosforge.org) > _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
