On Wed, 2005-02-16 at 09:54, Ben Collins-Sussman wrote:
> On Feb 16, 2005, at 5:35 AM, Zé Carlos wrote:
>
> > Hi,
> >
> > My svn server requires access through https and when running the svn
> > client like:
> > svn checkout https://myserver/svn/my_proj/trunk/ .
> > I Always get the error
> > svn: Unrecognized URL scheme 'https://myserver/svn/my_proj/trunk'
> >
>
> Build your neon library with ssl support. Configure either neon or
> subversion '--with-openssl'.
Building with SSL seems to be a recurring trouble spot for new users. What do you all think about updating the INSTALL file with some of the examples from the following old post?
----------------------------------------------------------------------------
From:
Alan
Thompson
<alanwork04@whitecaps.net>
Reply-To:
alanwork04@whitecaps.net
To:
svn-users
<users@subversion.tigris.org>
Subject:
Apache2 +
Subversion +
SSL install
on Debian -
HOWTO
Date:
Tue, 02 Nov
2004
21:03:43
-0800
Hi - I just set up Apache-2.0.51 and Subversion-1.1.1 using SSL
(OpenSSL) on a Debian Linux system after some difficulty. I had
problems with apparent errors in the INSTALL file, which I finally got
sorted out with the help of some old (2003) messages in the mail
archives and a lot of trial and error (I have done about 6 non-ssl
Apache/Subversion installs before trying this install).
Since I didn't see a good HOWTO anywhere, I thought I'd contribute this
concise summary to the list. You may wish to type the following
commands into a short "go.csh" script in the top-level directory of each
source tree, and then execute the script (rather than typing each
command individually). This can be very helpful if you need to tweak
paths, flags, etc for multiple build attempts.
In particular, the usage and interaction of the --enable-ssl,
--with-ssl, and --with-libs flags was not well-documented in either the
INSTALL file or by "./configure --help". Note that the syntax of the
--with-ssl flag is different in the Apache and Subversion builds.
Here are the steps I used, in the order that I executed them:
OpenSSL (http://www.openssl.org):
----------------------------------------------------------------
./config
make
make test
make install
----------------------------------------------------------------
Apache2 (http://httpd.apache.org/):
----------------------------------------------------------------
./configure --enable-dav --enable-so --enable-deflate \
--enable-ssl --with-ssl=/usr/local/ssl
make clean
make
make install
----------------------------------------------------------------
Subversion (http://subversion.tigris.org/):
----------------------------------------------------------------
./configure --with-zlib --enable-ssl --with-ssl \
--with-libs=/usr/local/ssl:/usr/local/ssl/lib:/usr/local/lib:/usr/lib:/lib
make clean
make
make install
----------------------------------------------------------------
After building from the three source trees, add the following lines to
the bottom of the Apache httpd.conf file as described in section III.C
of the Subversion INSTALL file (circa line 1056).
<Location /svn/repos>
DAV svn
SVNPath /absolute/path/to/repository
</Location>
Note that the subversion "make install" command apparently takes care of
putting the following line into httpd.conf:
LoadModule dav_svn_module modules/mod_dav_svn.so
Also, note that Apache must be started by:
/usr/local/apache2/bin/apachectl startssl
(rather than just "apachectl start") in order for https:// addresses to
be accepted.
I hope this helps.
Alan Thompson
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 16 22:44:10 2005