RE: [squid-users] Squid/NTLM and site timeouts

>> In regards to this log entry:
>>
>> 1329010018.324 1 192.168.71.117 TCP_DENIED/407 4067 GET http://www.pendulus.org/loadshortpause.php - NONE/- text/html
>> 1329010018.473 0 192.168.71.117 TCP_DENIED/407 4332 GET http://www.pendulus.org/loadshortpause.php - NONE/- text/html
>> 1329010048.720 30194 192.168.71.117 TCP_MISS/200 330 GET
>> http://www.pendulus.org/loadshortpause.php jgauthier
>> DIRECT/69.135.186.43 text/html
>>
>> Except the server is contacted at 1329010018, not 1329010048.

>Correct.

>The access.log timestamp is when the response is completed. The request arrived at Squid at timetamp - duration.

>In the above numbers the request was parsed by Squid at

> 1329010048.720 s - 30194 ms = 1329010018.526 s

>and forwarded slightly after.

Understood. Thanks. Is there anything I can do? If, for instance, a user tries to upload a file that takes longer than two minutes the NTLM connection breaks, and they are prompted with new credentials, and the upload is aborted. This is more real life than my test scenario, but that still happens, too.

I attempted to add "persistent_request_timeout 6 minutes", but that did not achieve the desired effect.

Thanks,

Jason


Received on Sun Feb 12 2012 - 19:01:14 MST