Hey Tory,
I am not aware of such changes from 3.5.16 to 3.5.17.
I have not tested for this case yet and it seems a bit weird for me to
see such behavior from squid.
I will be able to add it to the set of tests I already have later, until
now 3.5.17 looks pretty working to me and without known regressions.
Eliezer
On 04/05/2016 02:12, Tory M Blue wrote:
My configs have always consisted of http_port 80 accel vhost.. With
the latest 3.5.17 (I guess) if you don't list 0.0.0.0:80 squid won't
even attempt to listen, talk on ivp4..
So adding 0.0.0.0:80 allows it to at least talk via ipv4.
This seems wrong, odd.
I understand you are removing methods to disable ipv6, however forcing
folks to us only ipv6 seems like a stretch :)
Thanks
Tory
CentOS 7
squid-3.5.17-1.el7.centos.x86_64
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
