Re: New Auth configuration options

On Wed, 7 Apr 2010 20:27:38 +0100, "Markus Moeller" wrote: > Hi, > > Would it make sense to define in squid two new configuration options to > control Negotiate authentication ? I am thinking of adding > > Negotiate-NTLM > > and > > Negotiate-Kerberos > > with the same options as Negotiat

Build failed in Hudson: 3.HEAD-i386-opensolaris-SunStudioCc #186

See Changes: [Automatic source maintenance ] SourceFormat Enforcement [Amos Jeffries ] squidclient: Use -k option to control connection keep-alive or close This is needed to prevent HTTP 1.1 servers (or Squid)

New Auth configuration options

Hi, Would it make sense to define in squid two new configuration options to control Negotiate authentication ? I am thinking of adding Negotiate-NTLM and Negotiate-Kerberos with the same options as Negotiate. Once squid receives a Negotiate response quid has to base64 decode the token an

Build failed in Hudson: 3.HEAD-i386-opensolaris-SunStudioCc #185

See Changes: [Amos Jeffries ] squidclient: Use -k option to control connection keep-alive or close This is needed to prevent HTTP 1.1 servers (or Squid) holding the connection open after squidclient has finished

Build failed in Hudson: 3.HEAD-i386-opensolaris-SunStudioCc #184

See Changes: [Amos Jeffries ] Author: Matthew Morgan Add acl support to range_offset_limit. It is being parsed using the same data types as reply_body_max_size, which means the limit value gets run through pars

Build failed in Hudson: 3.HEAD-i386-opensolaris-SunStudioCc #183

See Changes: [Amos Jeffries ] HTTP1.1: Advertise 1.1 on replies [Amos Jeffries ] Cleanup: wrap more helpers with safety code [Amos Jeffries ] Compat: permit LDAP helepr to use std memory allocators --