[squid-users] CONNECT & tcp timeouts

Dear all,

I face a "subtle" issue with the way squid (2.2S5 & 2.5S1) handles tcp
connection timeout with the CONNECT method:
- 'GET ...' to a down webserver produces a 504 status code
- 'CONNECT ...' to a down webserver doesn't: once the tcp timeout occured squid
simply closes the tcp session (FIN) with the client.
Is there a reason ?
With Internet Explorer, proxy authentication and a proxypac listing several
proxies for redundancy it generates some issues: IE understand this session
ending as a signal to use another proxy (as if the proxy was down).
Some other proxies would generate a 504 or 500 error (NetApp for instance).

Regards
C. Bruneteau
Received on Mon Dec 23 2002 - 05:27:31 MST