Thanks for the quick response.
I understand the credential caching that svn does. What's additionally
needed is authentication state caching. Most svn user actions require
multiple http/https requests. Without any caching of the authentication
state each request has to be authenticated separately. If the authn
backend is a networked resource then the otherwise spiffy svn request turns
into molasses.
Perhaps the best solution for us is to use svn+ssh://
Thanks,
steve
> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: 15 February, 2005 14:19
> To: Stephen Willey
> Cc: users@subversion.tigris.org
> Subject: Re: SVN and htp/https cookies?
>
>
> On Feb 15, 2005, at 4:06 PM, Stephen Willey wrote:
>
> >
> > To save me from doing the test myself does anyone know if
> the svn unix
> > client will handle http/https cookies in a browser-ish way?
> In other
> > words
> > can I give the initial https response a cookie and hav it returned
> > with the
> > subsequent requests from the instance of the client?
> >
> > Do to the stateless nature of http/https and the latency in network
> > based
> > authentication mechanisms it is necessary to hav
> authentication state
> > cached
> > somewhere. Tying cached state to user sessions is commonly
> done with
> > cookies.
> >
> >
>
> There are no cookies. But svn does have a generic authentication
> caching mechanism, both for normal username/passwords and SSL certs.
> Read all about it in chapter 6 of the book.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 15 23:47:57 2005