At 23.42 08/09/2003, Henrik Nordstrom wrote:
Or to be more precise: "max_challenge_reuses 0" is supposed to deny the reuse of challenges, and in such configuration "max_challenge_lifetime" does not have any purpose.
Still there is no need for additional glue.
Not sure here: the Win32 security handles associated with the challenge response process have a lifetime, should Squid know this value ?
For long-term plans see earlier discussion regarding overlapping requests and NTLM. For Squid-3.1 we probably should throw out the whole challenge reuse layer and move this down to the helpers with the help of operlapping requests to the helpers, if at all needed.
Yes, I remember this thread.
Regards
Guido
- ======================================================== Guido Serassio Acme Consulting S.r.l. Via Gorizia, 69 10136 - Torino - ITALY Tel. : +39.011.3249426 Fax. : +39.011.3293665 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
