[squid-users] SQUID with cache_peer config + E2guardian - too many connections

[Matus UHLAR - fantomas]

>> On 29/07/20 8:29 pm, Klaus Brandl wrote:
>> > Setting an other "visible_hostname" may also help.

>On Wednesday 29 July 2020 23:03:43 Amos Jeffries wrote:
>> Why do you think the hostname has any relation to the problem?

On 29.07.20 13:58, Klaus Brandl wrote:
>because we had also a forwarding loop by connection 2 squids on the same host
>together via a parent statement. Then in the via header there was the same
>hostname 2 times, and this issued squid to detect a forwarding loop.
>Setting an other visible_hostname on one of the squids solved this problem.

there's a specific setting "unique_hostname" for these cases.

#  TAG: unique_hostname
#       If you want to have multiple machines with the same
#       'visible_hostname' you must give each machine a different
#       'unique_hostname' so forwarding loops can be detected.
#Default:
# Copy the value from visible_hostname


I just wonder why is this not set to $HOSTNAME by default, so setting same
visible_hostname on different servers would not require setting different
unique_hostname

-- 
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
The only substitute for good manners is fast reflexes.