On 10/06/11 09:34, errno wrote:
I've got squid conf that looks a bit like the following snippet:
# ...
acl ip-192.168.1.2 myip 192.168.1.2
http_port 192.168.1.2:80 name=ip-192.168.1.2
http_port 192.168.1.2:8080 name=ip-192.168.1.2
tcp_outgoing_address 192.168.1.2 ip-192.168.1
# ...
On Friday, June 10, 2011 02:20:49 AM errno wrote:
* the single instance listening on multiple ip:port http_ports:
192.168.1.2:80, 192.168.1.2:8080, 192.168.1.2:80 and
192.168.1.2:8080
Damn, that should have said:
* the single instance listening on multiple ip:port http_ports:
192.168.1.2:80,
On 10/06/11 21:20, errno wrote:
On Friday, June 10, 2011 12:07:49 AM Amos Jeffries wrote:
On 10/06/11 09:34, errno wrote:
I've got squid conf that looks a bit like the following snippet:
# ...
acl ip-192.168.1.2 myip 192.168.1.2
http_port 192.168.1.2:80 name=ip-192.168.1.2
http_port
On Friday, June 10, 2011 07:33:07 AM Amos Jeffries wrote:
snip
... behaved as intended: when clients went through
the http_port listener 192.168.2.2:80, the tcp_outgoing_address
worked as expected, wherein http://www.whatismyip.com
displayed 192.168.2.2 rather than 192.168.1.1.
*
I've got squid conf that looks a bit like the following snippet:
# ...
acl ip-192.168.1.2 myip 192.168.1.2
http_port 192.168.1.2:80 name=ip-192.168.1.2
http_port 192.168.1.2:8080 name=ip-192.168.1.2
tcp_outgoing_address 192.168.1.2 ip-192.168.1
# ...
Question: do those http_port directives