RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Even when specified the connect_timeout option squid does not "find another path where to forward the request." - as is written in the documentation

When it receives both protocol IPs it tries IPv6 first (or IPv4 when dns_v4_first specified), but when the connection timeouts squid sends its error webpage. 

Version-Release number of selected component (if applicable):
squid-3.1.10-12.el6

How reproducible:
always

Steps to Reproduce:
1. start squid with default configuration
2. request site with more address protocols defined but with preferred inaccessible.
  
Actual results:
Squid error webpage
The requested URL could not be retrieved
Connection to XXX failed

Expected results:
Squid should fallback to another protocol.
Requested webpage via another protocol

Additional info:
You can test it on ipv6.redhat.com which is inaccessible from our network on IPv6 so the request should fallback to IPv4. Same way it works also with /etc/hosts

Please note, that default behavior of clients *IS* to fallback by default (curl, firefox), so squid should do that automatically to. 

My first impression was, given by documentation, that this is done by the connect_timeout option. If not and the fallback is supposed to be configurable and disabled by default, consider this bug as RFE.

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

*** Bug 1087074 has been marked as a duplicate of this bug. ***

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days