On Tuesday, October 07, 2014 7:39 PM, Stefan Küng wrote:
> On 07.10.2014 17:11, Andy Gibbs wrote:
>> I'm having problems setting up TortoiseSVN with my SVN server. The
>> is running Apache Subversion 1.8.10 (r1615264) and Tortoise is the latest
>> (1.8.8/25755, 32bit). The server is set up with the following
>> <Location /svn>
> <Location /svn/>
> If you omit the trailing slash, a redirect is required which can confuse
> svn and tsvn.
Thanks for the advice, but this didn't help and unfortunately it also had
the side-effect that web-browsing to https://server/svn then failed too
(requiring now, of course, a trailing '/'). Tortoise gave a similar sort of
error anyway (included in case this helps anyone else googling this error):
Unexpected HTTP status 405 'Method Not Allowed' on '/svn'
Additional errors: PROPFIND request on '/svn' failed: 405 Method Not Allowed
Interestingly, Tortoise seems to strip the trailing '/' in any case.
However, I did notice a few interesting things in further testing.
It is worth mentioning, since I missed doing so in the earlier post, that
when pointing Tortoise at https://server/svn (and assuming no authentication
data is stored), firstly it asks for the username/password using the
Tortoise "Authentication" popup box. Then, even if I tick "Save
authentication", I would then get two Windows-style username/password
requests (i.e. the sort you would see for accessing a network share, for
example). I expect this is because the server is set up to support Kerberos
SSO, but this only happens when going to the parent folder, not when
accessing a repository directly.
Having observed this, I got a machine up-and-running with SSO properly
enabled in Internet Explorer. Suddenly everything worked perfectly -- no
user-visible authentication requests, and the parent repository list
Going back to my original machine, which doesn't support SSO, I discovered
that actually Tortoise only fails on the first attempt. This means --
either on opening the repository browser directly to the parent directory,
or opening the repository browser to the repository and then changing the
path to the parent directory. This fails as stated before. Then if I go to
the URL bar and re-enter the URL (sometimes it is even missing) then it
works reliably until the repo browser is restarted.
So, I don't know whether the problem then is simply Tortoise cannot handle
apache's kerberos authentication module properly if the client machine
doesn't support SSO. Anyway, I have a work-around for now.
Thanks for your help!
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-10-11 03:04:51 CEST