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

Re: should we really ship serf as default for 1.7? (was: Re: serf and sourceforge.net don't get along)

From: <kmradke_at_rockwellcollins.com>
Date: Fri, 24 Jun 2011 08:55:02 -0500

Mark Phippard <markphip_at_gmail.com> wrote on 06/24/2011 08:50:22 AM:
> On Fri, Jun 24, 2011 at 9:48 AM, <kmradke_at_rockwellcollins.com> wrote:
>
> > Is anybody using serf with negotiate authentication? I can't get it
to
> > work with a 1.6.5 server using mod_auth_kerb and negotiate.
> >
> > The server sends the 401:
> >
> > WWW-Authenticate: Negotiate
> > WWW-Authenticate: Basic realm="my realm"
> >
> > correctly, but serf just keeps re-sending the same original
> > unauthenticated
> > request. Works fine if negotiate is removed, and works fine either
way
> > when switched to use neon.
> >
> > I tested with the collabnet 1.7.0-dev build r1136035. User agent
shows:
> > SVN/1.7.0-dev serf/0.8.0
>
> I am not building with Kerberos. Wouldn't I need to compile with that
> for the support to be included? I would try the TortoiseSVN nightlies
> as I think Stefan includes GSSAPI in his builds.

Not sure, but I know serf shouldn't keep sending the same endless
unauthenticated request until I control-C the command. No indication
it was even doing anything until I put a proxy in between to sniff
the traffic...

In any case, it wasn't choosing BASIC either, even though it was
offered...

Kevin R.
Received on 2011-06-24 15:55:36 CEST

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

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