Search squid archive

Re: Squid+IWSS HTTPS header problem.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

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.
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)?

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

Regards,
Juan Pablo.


Chris

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux