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

RE: [Subclipse-users] JavaSVN and http:// protocol

From: Alexander Kitaev <alex_at_tmate.org>
Date: 2006-04-10 15:46:39 CEST

> Does that all sound about right?
The only problem with all that is that you didn't get nor correct error
message, neither authentication prompt dialog. I.e. subversion server was
considering cached credentials as "valid" but at the same time reported "not
found" error instead of "non authenticated" one. I think it is more
Subversion problem, may be it makes sense to upgrade to the 1.3.1 version.

Regarding credentials caching - from my point of view it is very convenient
(comparing to prompt on each http request), and when both server and client
works as expected one should get credentials prompt dialog when "cached"
credentials are not valid.

Alexander Kitaev,
TMate Software,
http://tmate.org/
http://jetbrains.com/tmate/

> -----Original Message-----
> From: Bradley Wagner [mailto:bradley.wagner@hannonhill.com]
> Sent: Monday, April 10, 2006 15:19
> To: users@subclipse.tigris.org
> Subject: Re: [Subclipse-users] JavaSVN and http:// protocol
>
> Guys, thanks for the responses. I think I've resolved it. I
> had forgotten that Subclipse does some strange connection
> "caching". For example, if you enter the wrong password, it
> usually remembers that incorrect password until the next time
> you start Eclipse even when the "save information" checkbox
> is unchecked.
>
> Anyway, I think tried to connect to the server using JavaSVN
> before it was finished intializing, thus the initial error.
> In a few minutes I switched to JavaHL and connected
> successfully. When I switched back to JavaSVN and tried again
> I got the original error about the failed connection. The
> problem resolved itself immediately after I restarted Eclipse.
>
> Does that all sound about right?
>
> Bradley
>
> On Apr 10, 2006, at 9:07 AM, Mark Phippard wrote:
>
> > "Alexander Kitaev" <alex@tmate.org> wrote on 04/10/2006 07:55:33 AM:
> >
> >> I never received similar reports before and in general
> http protocol
> > support
> >> works fine, so it looks like there is something specific in your
> >> environment. What URL do you use to connect to repository?
> Where this
> > %PATH
> >> ON SEVER% could come from? What operation do you perform
> when you get
> > this
> >> error message?
> >>
> >> If possible, please get JavaSVN debug log (set log level
> to FINEST in
> >> JDK_HOME/jre/logging.properties and specify file to save
> log messages
> >> to there, then restart Eclipse).
> >
> > I wonder if it is possible that the server is looking at how the
> > client is identifying itself in the request header? Maybe it is
> > specifically looking for the typical Subversion header and
> rejecting
> > other clients?
> >
> > Mark
> >
> >
> >
> >
> ______________________________________________________________________
> > _______
> > 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
> >
>
>
> --
> Bradley Mitchell Wagner
> Software Developer
> email: bradley.wagner@hannonhill.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Apr 10 15:46:59 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.