Right Graeme !! that was the problem. I don't know how is the parent proxy, but what I know is that it has three IP addresses. What I've done is to use just one of the three IP addresses in my squid.conf file instead of hostname:
#cache_peer proxy.jclm.es parent 8080 0 proxy-only default no-query no-digest cache_peer 142.10.1.10 parent 8080 0 proxy-only default no-query no-digest Just one more thing, I suppose that the parent proxy could be a cluster or a server machine with three network cards so I'd prefer to use the hostname in my 'cache_peer' line in the squid.conf file because maybe in that way the server balance the load and it's better in performance. The way I've solved the problem I'm always sending all our request to the same IP address and maybe that's worse in performance. I don't know. Besides, this problem is just for https/ssl (Banks) sites, the rest of the https/ssl sites and http (not encrypted) sites are ok using the hostname of the parent proxy. Is there any option in the squid.conf file to avoid this problem just for the https/ssl sites ?? I'll register the bug, anyway. Thanks for all your help, Fernando. El mi�, 28 de 05 de 2003 a las 15:57, Graeme Wood escribi�: > On 28 May 2003, Fernando Ruza wrote: > > > Ok Henrik, however it happens the same with my Mozilla browser (mozilla > > 1.3) from my linux laptop box. > > > > Thanks, > > Is your proxy a cluster of machines or are you using a parent proxy that > may be a cache cluster? Some banks will check that the connection is > coming from the same IP address, and if you are going through a cache > cluster, subsequent connection attempts may be coming from different IP > addresses. > > Cheers > Graeme -- Yo uso software libre, �Y tu? �Qu� es el software libre? consulta: http://www.gnu.org/philosophy/free-sw.es.html Fernando Ruza e-mail: [EMAIL PROTECTED] Tlf: 661123845 Yahoo! Messenger id: fruza Linux user: #273644 (http://counter.li.org) Debian Sid (Kernel 2.4.20 & ext3) "In an internet without fences ... who needs 'gates'"
