lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: squid (Ubuntu Lucid)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Robert, are you working on a fix ?
** Tags added: lucid regression-release
** Tags removed: regression-potential
** Also affects: squid (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: squid (Ubuntu Lucid)
Status: New = Confirmed
** Changed in: squid (Ubuntu
Wasn't arbitraty. But it incorrectly considered a Host: header without
port as no port specified and then fell back on vport or socket port in
order.
--
squid in lucid adds bogus port number to Host: line if one isn't provided (in
original or via vport=)
https://bugs.launchpad.net/bugs/640511
Confirming, because it was confused :). We'll want to put this patch in
the 2.7 packages; it is surprising sysadmins.
** Changed in: squid
Status: Invalid = In Progress
** Changed in: squid (Ubuntu)
Status: Invalid = Confirmed
--
squid in lucid adds bogus port number to Host:
This is a feature designed for maximum compatibility with other
software.
From squid developer discussions:
hno:
default port in accel mode is the listening port unless told otherwise by the
host header or vport. If you run Squid on port 3128 but it's actually
processing port 80 requests then
It is not clear to me which Squid versions this relates to.
Looked over the vport logics one more time, and squid-2 did behave a bit
odd and unexpected there. Squid-2 HEAD/trunk patch which should fix this
at http://www.squid-cache.org/Versions/v2/2.HEAD/changesets/12698.patch
and probably
@Amos defaulting the port is one thing; setting it rather arbitrarily
in the forwarded header is another thing altogether.
@Henrik - thanks for finding that, I'll have a poke shortly at it.
--
squid in lucid adds bogus port number to Host: line if one isn't provided (in
original or via vport=)
