ons 2008-01-09 klockan 18:05 +1300 skrev Amos Jeffries: > Nice in principle, the problem becomes how to do it cleanly. Given that > timeout is known only to client/server side, and the whole ipcache > stands between the resolver and the point of most desirable lookup.
Not really. Connect timeouts & failures is supposed to be handled by the commConnect state machine, which also is the one performing the DNS lookup.. But yes, it's not done very good and there is also a timeout managed by the caller, and due to timing connect timeout is usually handled there.. To get the connect timeout handled by commConnect you need to either set connect_timeout larger than your OS default connect timeout, or fix Squid to tune the os timeout.. But it can be done cleanly within ipcache alone while ignoring the whole timeout mess, by performing the A lookup if ipcache finds an entry where all addresses is marked bad and there has not yet been an A lookup performed. Regards Henrik
signature.asc
Description: Detta är en digitalt signerad meddelandedel
