enterprise-support team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

It appears this bug is fixed in 3.5.1, which Robie Basak is syncing from debian.
I've tried to reproduce but have not been able.  When robie fixes bug 1473691, the fix should come into xenial (16.04).

We can look upstream to find what fix this actually was and cherry pick
back to 14.04.



** No longer affects: squid-deb-proxy (Ubuntu)

** Also affects: squid3 (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Also affects: squid3 (Ubuntu Xenial)
   Importance: Undecided
       Status: Confirmed

** Also affects: squid3 (Ubuntu Wily)
   Importance: Undecided
       Status: New

** Changed in: squid3 (Ubuntu Trusty)
       Status: New => Confirmed

** Changed in: squid3 (Ubuntu Wily)
       Status: New => Confirmed

** Changed in: squid3 (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: squid3 (Ubuntu Xenial)
       Status: Confirmed => In Progress

** Changed in: squid3 (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: squid3 (Ubuntu Wily)
   Importance: Undecided => Low

** Changed in: squid3 (Ubuntu Wily)
   Importance: Low => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to squid3 in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1547640

Title:
  proxy tries ipv6 and gets 503 when no ipv6 routes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+subscriptions