Re: NTLM patch

Can you please describe the problem cause and workaround for POST?

The second problem sounds like a serious error. Maybe memory curruption
related to request_t structures.

Hmm.. is this a child cache or a directly connected one with no parents?

Are you using any redirectors?

Do you have a access.log entry from a failed reqest? Which site does it
show?

I plan on finding time to look into the details of your NTLM changes
later on. I have archived a copy of your patch from 14 december. If you
have a newer version please send it here.

--
Henrik Nordstrom
Squid hacker
Andy Doran wrote:
> 
> I've taken the NTLM patch down off dns1.sports.gov.uk. There exist
> problems with POSTing (as I've said before) and occasionally request
> ordering (e.g. type www.yahoo.com and get www.compaq.com, which somebody
> else just requested).
> 
> The code is and always was a hack, anyway.
> 
> I have a workaround for the first problem. Unfortunately I can only
> reproduce the second on a production system - the f-ckwits that represent
> senior management where I'm working have been bitten by it, so it's had to
> be ripped out.
> 
> Given the above and my lack of Squid expertise I can't do much more about
> this. Well, at least there exists an understanding of how NTLM
> authentication works.
> 
> Sorry, folks.