On 11 November 2013 18:03, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 11.11.2013 16:28, Bob Archer wrote:
> >> Hello we want to update our TortoiseSVN to version 1.8.3 build
> >> 24901. For this i'm testing the compatibility to our 1.6
> >> repository.
> >> With the newest Version most of the earlier problems are solved.
> >> The only problem i didn't find a solution for is the Repo-browser.
> >> Our repositories are installed on a server which can't be reached
> >> by HTTP/HTTPS. Also our users don't have accounts on this server.
> >> We use the pathdepending authorizaion of SVN.
> >> With the new version of TortoiseSVN the Repo-Browser automaticaly
> >> try's to get a connection to the repository by HTTPS. Canceling the
> >> login is not possible (repeats the opening of a Login window) and
> >> closing the Repo- browser result in a no longer responding Explore
> >> which only can be killed over the Taskmanager.
> > I'm not sure what you are saying... depending on how you access the
> > repo browser you are fully in control of what protocol it uses. If
> > you invoke the repo browser by right clicking on a working copy, it
> > will use the remote path info in the working copy to connect to the
> > server. So, if the working copy was checked out from http:// or
> > https:// that is what TSVN will use. You may need to "relocate" your
> > working copy if it is pointing to a server using an incorrect
> > protocol. You can look at the URL of your working copy by right
> > clicking on it, choosing, properties, and then going to the
> > Subversion tab. If the URL starts with http:// then you should use
> > the TSVN-> Relocate command to correct it to the svn:// protocol.
> > If you invoke the repo browser from a non working copy, like desktop,
> > a URL box comes up, asking for the path of the repository. It is
> > going to use whatever protocol you specify in that path... so be sure
> > to use svn:// there.
> I think the problem here is that the repo browser tries to fetch the web
> page generated by the SVNParentPath directive if it can not access the
> passed url. In that case it assumes that it may not be the repository
> but the page that lists all the repositories under SVNParentPath.
> I'll add an option to disable this behavior:
> I think the OP is saying that he doesn't even use http/s. Doesn't
SVNParentPath only work on Apache and not svnserve?
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-11-12 10:31:30 CET