[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: Ivan Zhakov <ivan_at_visualsvn.com>
Date: Fri, 24 Jun 2011 19:50:15 +0400

On Fri, Jun 24, 2011 at 17:50, Mark Phippard <markphip_at_gmail.com> wrote:
> 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.
serf uses SSPI for Kerberos on Windows and it should be automatically
enabled if your build serf 0.7 or later on Windows. I've tested
Negotiate (Kerberos) authentication in TortoiseSVN using serf in our
environment and it works in simple cases.

Ivan Zhakov
Received on 2011-06-24 17:51:08 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.