Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 333073 - net-proxy/squid-3.1.6-r1 broken with -ipv6
Summary: net-proxy/squid-3.1.6-r1 broken with -ipv6
Status: RESOLVED DUPLICATE of bug 331965
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Network Proxy Developers (OBSOLETE)
Depends on:
Reported: 2010-08-16 21:02 UTC by Will B.
Modified: 2010-08-17 19:22 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Will B. 2010-08-16 21:02:05 UTC
If the system is built with the -ipv6 flag, the latest stable Squid proxy is broken for HTTPS requests.  This appears to be a known bug - the URL reflects a similar bug filed with Debian.

Reproducible: Always

Steps to Reproduce:
1. Build system with -ipv6
2. Attempt to access an HTTPS site using Squid

Actual Results:  
The following error was encountered while trying to retrieve the URL:*

Socket Failure

The system returned: (97) Address family not supported by protocol

Squid is unable to create a TCP socket, presumably due to excessive load. Please retry your request.

Your cache administrator is root.

Expected Results:  
Access to the website.

The upstream bug seems to indicate that it's fixed in 3.1.3, but that doesn't appear to be the case in Gentoo world (and perhaps not upstream either).  I'm currently rebuilding my system with +ipv6 to confirm that works.

Another host system of mine is built with +ipv6 and I didn't trigger this issue, leading me to believe that is indeed the fix.  I'll update in an hour or so when everything rebuilds.
Comment 1 Will B. 2010-08-16 21:03:24 UTC
Further reading into the upstream bug indicates that might be a separate issue specific to DNS handling.
Comment 2 Will B. 2010-08-16 22:59:36 UTC
Rebuilt with +ipv6 and everything works as expected.  That would appear to be the workaround.
Comment 3 Alin Năstac (RETIRED) gentoo-dev 2010-08-17 19:22:16 UTC

*** This bug has been marked as a duplicate of bug 331965 ***