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

Greetings, Ryan C. Gordon!

> 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

This is known issue and i've found a way around it. Search in archive.

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

There's nothing wrong, really. Subversion built to be used with http://
access, svn:// is just a fallback for those who can't use Apache.

> 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.

Better is, yeah, let Subversion run on http:// and install viewvc somewhere
else.

--
WBR,
 Andrey Repin (anrdaemon_at_freemail.ru) 09.05.2009, <1:14>
Sorry for my terrible english...
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2122371
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].