--- Chris Robertson <crobertson@xxxxxxx> escribió: > Juan Pablo Calomino wrote: > > Thanks Chris, > > > > Now, through Webmin, I've configured an ACL in > Squid > > so "Safe_ports" fetch directly, because IWSS > cannot > > scan it. > > > > Perhaps you meant to do SSL_Ports? > Yeah, SSL_Ports, I've corrected that later. > > Anyway, this is what i get when I try to go to > > https://www.bankboston.com.ar, and wait... > > > > 1169587631.483 440022 10.1.48.24 TCP_MISS/200 39 > > CONNECT www.bankboston.com.ar:443 - > > DIRECT/32.104.16.39 - > > > > More than 7 minutes elapsed and only 39 bytes sent > to the client. That > reads like a timeout error to me. Yeap, it times out, it's like replies never come to Squid. > > I see packets going out, but they never come back. > > I also have other proxies and they work ok, so it > > shouldn't be a FW problem. > > > > What kind of proxies? Any plain Squids (without > Websense integration)? > I have a InterScan VirusWall. In this case, my FW is integrated via URI resources to Websense. > > Maybe Websense is doing something wrong, but they > > don't say anything. > > > > That seems to be a common theme. > http://www.google.com/search?hl=en&q=websense+site%3Ahttp%3A%2F%2Fwww.squid-cache.org%2Fmail-archive&btnG=Google+Search > I've stopped Websense services, and Squid still does the same. > > Regards, > > Juan Pablo. > > > > > > Chris > This is not happening in just one server. I have three servers configured this way, and in all of them I have the same problem. Two are Linux Red Hat, and the third is a Solaris 8. All Squids are 2.5. Websense in linux are 6.11 version, and in Solaris is 6.3. I really don't know what's going on, because as I said, I see packets coming out, but never coming back. Juan Pablo. __________________________________________________ Preguntá. Respondé. Descubrí. Todo lo que querías saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas
