Handling http:// when you really want svn://

So my server has a virtual host, svn.icculus.org ...

svn://svn.icculus.org/ goes to the Subversion daemon, and
http://svn.icculus.org/ goes to viewvc.

Besides the protocol, the basic URLs are the same: svn://blah/Project
gets you Project repository, and http://blah/Project gets you a
human-friendly webview of Project.

The problem I'm running into is that people don't read carefully, or
have muscle memory to type "http" for URLs, or maybe just assume the web
view will map for a Subversion client the way that Mercurial does.

Many, many people have emailed me to tell me that "subversion is broken"
when they get things like this...

   $ svn ls http://svn.icculus.org/duke3d
   svn: Repository moved permanently to '/duke3d/'; please relocate

...when in fact, the problem is that they're using the wrong URL, and
talking to Apache without Subversion (or even WebDAV) support.

What's the best way to deal with this scenario? Ideally, I'd like the
svn client to realize that this server doesn't support PROPFIND and tell
the user "maybe you meant 'svn://blah/Project'?" or something, but I'm
not sure what's involved in that magic, or if there are better
approaches I could be taking on the server side.

Thanks,
--ryan.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2117788

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-08 20:13:15 CEST