[squid-users] peering

From: Hermann-Marcus Behrens <hermi@dont-contact.us>
Date: Wed, 27 Apr 2005 11:20:57 +0200

Hello,

I'm using the latest Squid 3 Beta (squid-3.0-PRE3-20050427) as a reverse
proxy.
I have one server which does heavy image-calculations (it renders maps,
2-3 seconds for each image). Now I
added a second server and I would like to use the "cache_peer" option so
that each web accelerator checks
first, if the requested image is already rendered on the other cache.

Unfortunatly I was not able to get this working. I tried to change the
"always_direct" option, but if I delete this option,
the cache is not working any more.

My configuration looks like this:

http_port 213.133.a.c:80 accel defaultsite=127.0.0.1

cache_peer 127.0.0.1 parent 80 0 no-query originserver no-digest
name=mydomain
cache_peer 213.133.a.b sibling 80 3130
cache_peer 213.133.a.c sibling 80 3130

acl my_domains dstdomain www.domain.de
cache_peer_access mydomain allow my_domains
http_access allow my_domains

always_direct allow all

Does someone know, how to get this working? Or is the combination of a
"reverse proxy" and the use of other caches in a hierarchy not possible?

Greetings from germany,

Hermann Behrens

-- 
Hermann-Marcus Behrens / citybeat.de
E-Mail:  hermi@citybeat.de
Web:     www.citybeat.de
Telefon: 0421 - 16 80 80 - 0
Fax:     0421 - 16 80 80 -80
Adresse: Zum Huchtinger Bahnhof 13 / 28259 Bremen
Received on Wed Apr 27 2005 - 03:16:13 MDT

This archive was generated by hypermail pre-2.1.9 : Sun May 01 2005 - 12:00:04 MDT