On Mon, Aug 31, 2015 at 04:09:25PM +0200, Andreas Korsten wrote: > * James McCoy wrote: > > As shown in the working example, an initial 401 is expected. The client > > should retry with the auth. The question is why that isn't happening. > > > > What does “svn --version” show? > > All clients I tried showed the same behaviour. The first one was:
Ok, so it's not a neon-specific issue.
> Apache access log:
>
> |${CLIENT_IP} - - [31/Aug/2015:15:37:41 +0200] "OPTIONS /svn-krb/${REPO}
> HTTP/1.1" 401 5444 "-" "SVN/1.8.10 (x86_64-pc-linux-gnu) serf/1.3.8"
>
> Client output:
>
> |svn: E120190: Unable to connect to a repository at URL
> 'https://${FQDN}/svn-krb/${REPO}'
> |svn: E120190: Error running context: An error occurred during authentication
With the 1.7 client, would you be able to provide the (sanitized) output
of “svn --config-option servers:global:neon-debug-mask=130 ls
https://${FQDN}/svn-krb/${REPO}” with both the pre-upgrade server and
the post-upgrade server?
Hopefully that will shed some light on why the client isn't retrying
with authentication.
Cheers,
--
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <[email protected]>
signature.asc
Description: Digital signature
