Hi Amos,
thanks for your answer.
> Every time we 'fix' this we get complaints from people wanting the
> opposite behaviour or suddenly getting breakage. We for now have this
> behaviour: Squid should obey Host: port when "vport" is given, and
> ignore it when vport is omitted (using http_port value if none is pulled
> in indirectly by vhost anyway), and override/replace it when "vport=N"
> is given.
>
> So your config tells Squid to use what Pound supplies (default 80). You
> can avoid that by either getting Pound to stop adding the unusual port
> to the header, or using vport=80 in squid.
Ahh ok, so it must be work, when i put vport=3007 and vport=3008 in my
config, right?
So, but this doesn´t work. In the cache.log i can see that squid try to
connect to sub3007 which resolved to 127.0.0.1 by etc/hosts to port 80.
I´m very confused about the situation that my config works with squid2.
Tim
Received on Fri Jul 22 2011 - 06:25:06 MDT
This archive was generated by hypermail 2.2.0 : Fri Jul 22 2011 - 12:00:03 MDT