Nate Parsons wrote on Fri, Feb 24, 2012 at 14:24:30 -0500: > On Fri, Feb 24, 2012 at 12:46 AM, Daniel Shahaf <danie...@elego.de> wrote: > > Nate Parsons wrote on Thu, Feb 23, 2012 at 16:46:55 -0500: > >> * ra_serf : Module for accessing a repository via WebDAV protocol using > >> serf. > >> - handles 'http' scheme > >> - handles 'https' scheme > >> > >> If there is any other information I could provide, let me know. > > > > Are you able to rebuild --with-neon and try again? I have no particular > > reason to suggest this, but it might help isolate the problem. > > > > (And see the ~/.subversion/servers:global:http-library config option) > > I couldn't before because my neon was too old, but I built the version > pulled down by svn's get-deps.sh, and now --with-neon works. My > --version output is now: > > * ra_neon : Module for accessing a repository via WebDAV protocol using Neon. > - handles 'http' scheme > * ra_svn : Module for accessing a repository using the svn network protocol. > - handles 'svn' scheme > * ra_local : Module for accessing a repository on local disk. > - handles 'file' scheme > * ra_serf : Module for accessing a repository via WebDAV protocol using serf. > - handles 'http' scheme > - handles 'https' scheme > > I didn't see any errors related to neon and https, so do I have to do > anything special to get https through neon? >
You need to build neon against openssl or gnutls. > On the plus side, neon and http work! Okay. Can you try now with serf (no need to rebuild, just pass --config-option=servers:global:http-library=serf) and a new repository? If you see the problem with a new repository, could you please file a bug against libsvn_ra_serf. (But if not, it could be that your repository's backend is at fault.) Thanks Daniel
