Package: suqid3
Severity: important
Summary:
the current squid3 packages are forcing users to manually override
the package patch or face HTTP denials from upstream proxies.
A good description of what users encounter is documented at
http://www.squid-cache.org/mail-archive/squid-users/201304/0112.html
Cause:
The squid3 package currently patches Squid to forces visible_hostname
to always be defined with a value of "localhost". This patch appears to
be the remnant from Squid-3.0 and older which could abort with FATAL
messages when visible_hostname is not successfully auto-detected.
However that issue has since been resolved upstream with a default of
"localhost" being used when gethostname() fails.
In the thread linked above the ubuntu keyserver machine and the test
proxy were both installed from Debian derived packages containing this
patch and left with the package defaults. In the working self-build the
patch was missing and auto-detection correctly identified the hostname
to differentiate the servers.
When visible_hostname is configured (manually or via this patch) the
Squid auto-detect functionality is completely disabled. Which requires
admin to manually override the patched visible_hostname with the
hostname which should have beent auto-detected.
Please remove this part of debian/patches/01-cf.data.pre.debian.patch
Amos
--- debian-3.3/patches/01-cf.data.debian.patch 2013-04-23 17:37:09.000000000
+1200
+++ debian-3.3.3-1/patches/01-cf.data.debian.patch 2013-04-23
17:53:30.000000000 +1200
@@ -83,15 +83,6 @@
DOC_END
NAME: emulate_httpd_log
-@@ -5268,7 +5271,7 @@
- NAME: visible_hostname
- TYPE: string
- LOC: Config.visibleHostname
--DEFAULT: none
-+DEFAULT: localhost
- DOC_START
- If you want to present a special hostname in error messages, etc,
- define this. Otherwise, the return value of gethostname()
@@ -7771,8 +7774,8 @@
WARNING:
