You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Ben Collins-Sussman <su...@collab.net> on 2004/08/03 12:41:41 UTC

RE: svn failure from remote machine (svn not using fully qualified 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 when
> the laptop was connected in the remote site the svn switch command tried
> 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
realm.  

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