When emerging >=squid-3.1.6 with USE="-ipv6", any attempt to access an SSL URL results in the error massage and the access fails.
Steps to Reproduce:
1.USE="-ipv6" emerge -av1 ">=net-proxy/squid-3.1.6"
3.Try to open a https Website
The access (allowed by squid ACL configuration) fails. Error message "comm_open: socket failure: (97) Address family not supported by protocol" in "/var/log/squid/cache.log".
No such error message. Access should be granted or denied depending on squid configuration, but not just fail due to a socket error.
Some people "fixed" that bug by re-enabling ipv6 in the kernel.
However, this is a kludge rather than a fix. Also, enabling or disabling IPv6 is a system-wide issue with all sorts of consequences, such as modified Firewall configuration.
Squid has a --disable-ipv6 configure option, and it should honor it.
Note that this is clearly an upstream bug. Nevertheless, it affects the functionality of the USE flag, so we might consider adding a patch.
*** This bug has been marked as a duplicate of bug 331965 ***