CODEWITHSUNDEEP
svn
c12
c12

Reputation: 9827

Issue Accessing SVN Repository with Both SVN and HTTP Protocols

I'm trying to access a SVN repository that I created (using svnadmin) on my local machine using the HTTP protocol, but I can't determine the URL. Is there additional configuration I need to supply to access it as HTTP? I have no issues accessing it using SVN protocol. I just want to do some performance tuning and compare the protocols. Any ideas? Commands used to create repo are below.

Repository Creation and Server Start Commands:

$cd
$svnadmin create my-repository
$svnserve -d -r /Users/myusername

SVN:

$ svn info svn://localhost/my-repository
Path: my-repository
URL: svn://localhost/my-repository
Relative URL: ^/
Repository Root: svn://localhost/my-repository
Repository UUID: 2de7b13c-0139-45f6-a121-4d8cc6918849
Revision: 86
Node Kind: directory
Last Changed Rev: 86
Last Changed Date: 2013-12-04 11:58:03 -0800 (Wed, 04 Dec 2013)

HTTP:

$ svn info http://localhost/my-repository
svn: E120108: Unable to connect to a repository at URL 'http://localhost/my-repository'
svn: E120108: Error running context: The server unexpectedly closed the connection.

Upvotes: 1

Views: 2845

Answers (1)

Ben Reser
Ben Reser

Reputation: 5765

You need to setup Apache httpd with mod_dav_svn.

In general svnserve will be faster than httpd. httpd is more popular because originally svnserve didn't support encryption except through ssh tunnels (it does now via SASL) and it didn't support nearly as many authentication methods (again SASL support changed this).

The only major feature that httpd has that svnserve doesn't is the ability to browse the repositories with a web browser directly (Note that this isn't the same as say browsing with viewvc).

One benefit of httpd is that since it uses HTTP it generally goes through firewalls without special configuration. It can also be proxied (allowing for a caching proxy to help speed it up).

Upvotes: 3

Related Questions