On Oct 19, 2004, at 10:03 AM, Molle Bestefich wrote:
> 1.)
> I have a handful of repositories set up, and I'm hunting for some sort
> of hack to allow the Repo-Browser in TortoiseSVN to enumerate and list
> the different repositories. Currently it returns '403 Forbidden' and
> '450 Method Not Allowed' whenever someone forgets a trailing slash or
> something similar, which kinda ruins the smooth end user experience.
The TortoiseSVN repo-browser is just running 'svn ls', browsing the
structure of a repository. There are no hacks to show all possible
repositories. 'svn ls' requires that you point it at *one* repository.
If you want a list of all repository URLs, you'll have to make
yourself a web page. Maybe something CGI-based.
>
> 2.)
> The Repo-Browser sends duplicate "Accept-Encoding: gzip" headers.
> Reproduce: Sniff using ethereal while repo browsing, apply this
> filter: 'http.request.method == "PROPFIND"'.
Hm, dunno if that's a problem, seems harmless. Still, it's a
curiosity. I wonder why.
>
>
> 3.)
> Setting up SVN was such a sweet deal.
You mean, 'svnserve'?
> Setting up the Apache access was hell on earth.
Would you like to be more specific? Is it just the error messages?
> Out of curiosity, why is it that it can't give proper error messages
> instead of these awful '450 not allowed', '403 forbidden' etc. things?
>
The apache server is perfectly capable of throwing human-readable
errors and messages generated by the svn libraries, and marshalling
them back to the client. But when the error is related merely to
apache misconfiguration, then -- surprise, surprise -- you're going to
see HTTP errors. It's an HTTP server, remember? :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 20 14:49:19 2004