Public bug reported:
| # TAG: visible_hostname
| # If you want to present a special hostname in error messages, etc,
| # define this. Otherwise, the return value of gethostname()
| # will be used. If you have multiple caches in a cluster and
| # get errors about IP-forwarding you must set them to have individual
| # names with this setting.
| #Default:
| # visible_hostname localhost
This isn't actually true, at least the part about gethostname().
It'll first do a reverse DNS lookup on the IP of the first http_port
entry (getMyHostname() in src/tools.cc) and only use get_hostname().
Our first http_port is 127.0.0.1 in a lot of places, so
visible_hostname is now localhost for those squids. This caused bogus
forward loop detection to kick in when our office squid tried to talk
to the squid that runs the Ubuntu Forums.
I'm not necessarily arguging that the current behaviour is wrong, but
it would be nice if the code and the docs could be consistent.
** Affects: squid3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1098641
Title:
visible_hostname defaults to hostname of first http_port IP, not
get_hostname()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1098641/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
