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

RE: svn failure from remote machine (svn not using fullyqualified server path?)

From: Krebs, Steven <steven.krebs_at_intel.com>
Date: 2004-08-03 22:05:58 CEST

How would I (and could I) delete just the cache file without deleting
the whole workspace?

(note: we were not using Apache... svn://<servername>/<repo>)



-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Tuesday, August 03, 2004 5:42 AM
To: Krebs, Steven
Cc: users@subversion.tigris.org; Pullen, Santosh
Subject: RE: svn failure from remote machine (svn not using
fullyqualified server path?)

On Tue, 2004-08-03 at 02:30, Krebs, Steven wrote:
> I think we figured it out...
> The original checkout was done on a laptop while it was connected
> locally and subversion cached the short name path (dpxlxb0002) and
> the laptop was connected in the remote site the svn switch command
> to use the cached short path.

"Cached the path?" The client only caches 3 things: the authentication
"realm" sent by the server, and the associated username/password for the

Aha. Now I get it. Apache creates a "realm" by concatenating the
host:port with the AuthName directive, so the client gets a realm like:

   <http://svn.collab.net:80> Subversion repository

So you're right, the only way to fix what was happening to you was to
disable the use of cached credentials.... which you did by deleting the
cache file, as expected.

The real problem here was figuring out that it was the authn cache
causing the problem in the first place. Fixing issue 1683 would fix
this problem... you would see a notification that the cache was being
used, and was failing.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 3 22:06:36 2004

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

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