Re: [squid-users] multiple web ports squid not working?

jason bronson wrote:
> I've got an issue where I have multiple ports one webserver is on port
> 80 and one is on 21080
> anyhow 21080 works fine
> port 80 from the outside world doesnt work at all i get a blank
> index.php file returned from the browser to download?
>
> So i run tcpdump on port 80 and i see connections coming in but squid
> is not writing anything to the logs even with full debugging?
>
> I run wget from my squid server to see if it can talk with the
> webserver and it returns the 21080 webserver page???
>
> what bothers me is I'd think at this point the outside world would at
> least see the 21080 server not a blank index file returned? and I'd
> think something would write in squids logs?
>
> Please if anyone knows what im doing shoot me a hint !
>
> Im running
> /usr/local/squid/sbin/squid -v
> Squid Cache: Version 2.7.STABLE3
> configure options:
>
>
> heres my configuration
>
> acl all src all
> acl manager proto cache_object
> acl localhost src 127.0.0.1/32
> acl to_localhost dst 127.0.0.0/8
> acl localnet src 10.108.0.0/24 # RFC1918 possible internal network
> acl SSL_ports port 443
> acl Safe_ports port 80 # http
> acl Safe_ports port 21 # ftp
> acl Safe_ports port 443 # https
> acl Safe_ports port 70 # gopher
> acl Safe_ports port 210 # wais
> acl Safe_ports port 1025-65535 # unregistered ports
> acl Safe_ports port 280 # http-mgmt
> acl Safe_ports port 488 # gss-http
> acl Safe_ports port 591 # filemaker
> acl Safe_ports port 777 # multiling http
> acl Safe_ports port 3128
> acl Safe_ports port 21080
> acl CONNECT method CONNECT
> http_access allow all

Absent any limits on the peers or direct access. This proxy is open for
abuse by anyone on the web.

> http_access allow manager localhost
> http_access deny manager
> http_access allow localnet
> http_access deny all
> icp_access allow localnet
> icp_access deny all

> http_port 80 accel defaultsite=64.132.59.237
> http_port 21080 accel defaultsite=64.132.59.237

defautsite= does not mean what you think.
It is the full domain name to be used of client omits the required Host:
header.

Unless you expect clients to access your website by
http://64.132.59.237/index.php that setting is incorrect.

DNS should be pointing your domain name at Squid.

> hierarchy_stoplist cgi-bin ?
> access_log /usr/local/squidserver/var/logs/access.log squid
> refresh_pattern ^ftp: 1440 20% 10080
> refresh_pattern ^gopher: 1440 0% 1440
> refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
> refresh_pattern . 0 20% 4320
> negative_ttl 0 seconds
> acl apache rep_header Server ^Apache
> broken_vary_encoding allow apache
> visible_hostname 127.0.0.1
> coredump_dir /usr/local/squidserver/var/cache
> cache_peer 10.108.50.39 parent 21080 0 no-query originserver name=mybox
> cache_peer 10.108.30.82 parent 80 0 no-query originserver name=webapps
> cache_peer_access webapps allow all
> cache_peer_access mybox allow all

> cache_peer_access webapps deny all
> cache_peer_access mybox deny all

These last two cache_peer_access lines are irrelevant given the ones above.

Given the order of peer defines, both having "allow all":
  * 10.108.50.39 will see nearly all requests arriving on its port 21080.
  * 10.108.30.82 will see few if any.
  * Squid will have requests arriving at both ports.

Amos

-- 
Please use Squid 2.7.STABLE4 or 3.0.STABLE9