-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 ICQ, like Skype later, uses special technique to bypass proxies/firewalls, and conventionally checks, after it native port 5190, other ports: 80,443,110,25 and other before it can connect to it's load balancer. Moreover, when use 443, it CONNECT over 443, but not use true HTTPS, just HTTP (squid writes it in cache.log). The problem is: ICQ is use not only own protocol-specific port 5190, but ANY other well-known port, and breaks standard usage of this ports. Squid can't pass this behaviour. I see no one squid.conf, which can be clearly pass ICQ. 27.10.15 0:27, Amos Jeffries пишет: > On 27/10/2015 6:30 a.m., Yuri Voinov wrote: >> >> I think the right question is not "What headers pass through Squid" and >> "Why did they pass through a transparent proxy, if the port that is >> used, not 80 or 443?" >> > > ICQ speaks HTTP on port 80. Not sure about 443, it should at least speak > TLS hopefully with ALPN and/or HTTP inside. > > Even so, whats going through (or at least into) Squid is the detail you > need to provide to get a chance at a solid answer. > > Amos > _______________________________________________ > squid-users mailing list > squid-users@xxxxxxxxxxxxxxxxxxxxx > http://lists.squid-cache.org/listinfo/squid-users -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWLnGxAAoJENNXIZxhPexGSYwH/3AUXCgAsQZH8atsFnzjVzFz oE/83spzQqA+81I9JmUfoAkjfQHNQeyl14OTGUubxnVcM5bd5DlKfxZVQR9rFMaR 6H1nPV1nmxTOgH2rrVBRA1TeaAx19HcitgND99WrjPJ2bNzUl/gZwvHFcuNflWh7 1cHJBG3G6tRbGpvKi3tWVjWuX2u+7Vbc2ABWuLzVf1scMdCm13D/qohIPfptPhat PPvAyqsrwStLPi86SH0R5N9+yfkAHbHqdcydacDvyrGWG1WrWIN8vCNB7NB3+Kts ao20X4tb8zv9pLo74obFUKfXdCG7p1ERJxYfuk/qejP/LA0iqKziS4kGyEoRE5A= =U0iw -----END PGP SIGNATURE----- _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
