Re: [squid-users] proxy cache with multi back end server !

I was thinking I've sent it before, anyway !
Here is my squid.conf based on the conf file from centos :

http_port 80 defaultsite=myserver
hierarchy_stoplist cgi-bin ?
acl QUERY urlpath_regex cgi-bin \?
cache deny QUERY
acl apache rep_header Server ^Apache
broken_vary_encoding allow apache
access_log /var/log/squid/access.log squid
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern . 0 20% 4320
acl all src 0.0.0.0/0.0.0.0
acl manager proto cache_object
acl localhost src 127.0.0.1/255.255.255.255
acl to_localhost dst 127.0.0.0/8
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 CONNECT method CONNECT
http_access allow manager localhost
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
cache_peer ip_server1 parent 80 0 no-query originserver name=server1
cache_peer ip_server2 parent 80 0 no-query originserver name=server2
acl foo urlpath_regex ^/foo
cache_peer_access server1 allow foo
cache_peer_access server2 deny foo
acl devmk_site dstdomain devmk.inria.fr
http_access allow devmk_site
http_access allow localhost
http_access deny all
http_reply_access allow all
icp_access allow all
coredump_dir /var/spool/squid

thanks again for your help :)

Henrik Nordstrom a écrit :
> tis 2008-04-08 klockan 09:54 +0200 skrev Mathieu Kretchner:
>> When I try to acces the second URL, Here is the error I get :
>> The following error occurred: Document not found (error number 404)
>
> Disable friendly error messages or use another browser than MSIE and you
> will keep more hairs on your head..
>
> I would guess the problem is that you haven't properly told Squid what
> to send to each peer so it ends up sending the request to the wrong one.
>
> What do your cache_peer_access rules look like?
>
> Regards
> Henrik
>