I tried that, but ICP doesn't seem to work, even though the other proxy is also a squid (1.1.22). When I try it, my proxy says that the other one is dead after a while, and the other proxy says things like 'WARNING: 143 of the last 150 ICP replies are DENIED' in its log. Any idea what could be wrong? I have the correct ICP port number for the other proxy in my config, but the host with the other proxy on it doesn't seem to be listening on that port, even though it should be according to its configuration files. Are there any known problems with ICP on a 1.1.22 squid? /Pepijn Karl Schaffarczyk wrote: > >On Mon, Mar 22, 1999 at 04:58:33PM +0100, Pepijn Schmitz wrote: > > > >> Couldn't find this one in the FAQ: how do I set up my squid (2.1.patch2) > >> so that it will always go to another proxy when it is available, but go > >> direct when it can't reach the other proxy for some reason? > > > >You can't, yet. 2.2 has a prefer_direct which would seem to fit the bill, > >but that release isn't ready yet. > > > >You're not alone in wanting this feature, believe me. :-) > > > > from my understanding, you simply configure a parent, with ICP on, and > let the squid route directly as well. If the parent replies in time, then > the parent is used, else, it goes direct. > > Regards > Karl > =8)
begin:vcard n:Schmitz;Pepijn tel;cell:+31 (0)6 53778794 tel;fax:+31 (0)35 5415591 tel;home:+31 (0)348 417919 tel;work:+31 (0)35 5422382 x-mozilla-html:TRUE url:http://www.xpuntx.nl/ org:X punt X b.v.;Software Engineering adr:;;Eemweg 6;Baarn;;3742 LB;The Netherlands version:2.1 email;internet:[EMAIL PROTECTED] title:software engineer x-mozilla-cpt:;-14272 fn:Pepijn Schmitz end:vcard
