[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn client doesn't ask for username and password with http ra_dav

From: Files <files_at_poetryunlimited.com>
Date: 2003-09-25 05:29:47 CEST

I will try to reproduce it again tomorrow. Anyone want to volunteer an RA_DAV
repository w/ a user name and password?

I know this happened to me at work.

Thanks.

Shamim Islam
BA BS

Ben Collins-Sussman (sussman@collab.net) wrote:
>
>Jack Repenning <jrepenning@collab.net> writes:
>
>> Someone else recently asked 'why does it cache login failures,' with
>> similar error indications.
>>
>> http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=45726
>> "Removing cached authentication tokens "
>>
>> If that's the same problem: there are hints there about cleaning up
>> the situation once it develops, but no insight into how it arose.
>
>Yeah, it's a mystery, because if you look at the code,
>
> 1. failed credentials should never be cached. bad credentials
> cause neon to re-ask for them, which causes the svn auth system
> to re-prompt. Eventually the svn auth system gives up on
> re-prompting and just throws an error back to neon, which means
> neon throws an error, which means the client dies. There's no
> opportunity to save them to disk.
>
> 2. if password changes on the server, the credentials on disk are
> bogus. but this just causes the auth system to revert to
> prompting.
>
>We still seem to have no reproduction recipe for this bug...
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: dev-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 25 05:30:46 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.