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

Re: [Subclipse-users] Authentication problem using Basic HTTP over HTTPS

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-02-10 15:13:41 CET

DM Smith <dmsmith555@yahoo.com> wrote on 02/10/2006 09:05:05 AM:

> Mark Phippard wrote:
> > http:// is a stateless protocol so every transaction starts over. If
> > choose to not cache the password, understandable, then you have to
enter it
> > on every transaction. You can try the JavaSVN adapter. For some
> > connection methods it does its own session-based caching, but the
> > adapter definitely does not.
> >
> Does Subclipse present the dialog?
> If so, couldn't it cache the password for the session, if the adapter is

> JavaHL?

It is harder than it sounds. We provide a callback class, but do not
really know when it is called or for what reason. Also it is called over
several calls, like one call to do the prompt and then different calls to
get the data that was entered. It is possible if we had some kind of
internal table keyed by the realm or something that we might be able to do
it, but the other problem is that we have no way of knowing if the
password was succesful or not.

This has been looked at in the past for other reasons.

Ideally the JavaHL library would do the caching since it knows all of this
and isn't like the library is being unloaded during the process.


Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Feb 10 15:14:28 2006

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

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