RE: [squid-users] Authentication to Sharepoint not happening

It works now! I followed the code and then turned "off pipeline_prefetch". In code there was this check which was setting no_connection_auth flag to 1.

if (Config.onoff.pipeline_prefetch)
    request->flags.no_connection_auth = 1;

I don't understand it completely but I can move forward. Thank You Amos!

Regards,
Saurabh
        
-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Tuesday, February 01, 2011 6:30 PM
To: squid-users_at_squid-cache.org
Subject: Re: [squid-users] Authentication to Sharepoint not happening

On 02/02/11 00:43, Saurabh Agarwal wrote:
> Looks like we are making progress. Yeah there is a condition in the code client_side.c that relates to when "WWW-Authenticate" header is being deleted. Condition checks for no_connection_auth flag in the request.
>
> This is the code. It checks if there is no_connection_auth in incoming request then that header is being deleted. I think it relates to pinning connections as you said earlier.
>
> if (request->flags.no_connection_auth) {
> httpHeaderDelAt(hdr, pos);
> connection_auth_blocked = 1;
> continue;
> }
>
> But in Squid-2.7.Stable7 there is support only for specifying no-connection-auth in http_port directive. In Squid 3.1 we can turn it on|off using connection-auth=[on|off].
>
> How to not set the no_connection_auth flag in Squid-2.7.Stable.7?

It is supposed to be on by default in both versions and the
configuration option there to turn it off and turn on stripping of the
header.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.10
   Beta testers wanted for 3.2.0.4