How can you expect *machineS* to get a response from squid if network is down? If squid is listening on localhost, the only client that can connect to it is the one on that machine. Any other client cannot connect to it. This would be a very isolated case I believe (squid after all is a cache, you might as well use your browser's cache for that purpose). No point in running squid for only 1 client. But I have not used squid windows, so I would not know the behaviour. Moreoever, I have not used squid in an environment where there is no internet connectivity 24/7. Another user pointed out that his squid on linux runs fine when network goes down. So this might be something with Windows. http://www.squid-cache.org/Doc/config/windows_ipaddrchangemonitor/ windows_ipaddrchangemonitor on Have you tried turning this config value this on/off? Jenny > Date: Mon, 11 Jul 2011 21:06:09 -0400 > From: january.sharp@xxxxxxxxx > To: squid-users@xxxxxxxxxxxxxxx > Subject: Re: Squid terminates when my network goes down > > Your analysis is correct and helpful, Jenny. Can you clarify further? > Are you saying that Windows machines running squid should not have > local web clients, i.e., not even set its browser to use the > locally-running squid? > > J > > On Sun, Jul 10, 2011 at 9:50 PM, Jenny Lee <bodycare_5@xxxxxxxx> wrote: > > > >> Is this a bug? If the network is down, shouldn't squid just generate > >> an error page, like ERR_CONNECT_FAIL, and not collapse like this? > > > > Logically, how would you expect squid to convey ERR_CONNECT_FAIL to the client if the network is down? > > > > I can think of only one case where this might make sense -- client connects from localhost to a squid listening on localhost but going out on other interface... which would mean a very isolated case of use for a cache like squid. > > > > Jenny
