> On 6/27/05, Ralf Hildebrandt <Ralf.Hildebrandt@xxxxxxxxxx> wrote: > > Is there a "default" solution for clustering multiple Squid proxies in > > a way that is transparent to the user? On 27.06 14:13, Kevin wrote: > The cheapest solution is to use round robin DNS records. If you > are using Cisco routers, you can look at IOS SLB, included in some > router feature sets. We are using nortel alteon switch for this. But the mentioned linuxvirtualserver has the same functionality (although probably not the same reliability) But maybe the DNS load balancing will be the same. > > We have 3 proxies, and "load-balance" the requests using a proxy.pac > > files. Unfortunately this doesn't work properly, since some people > > don't use that autoconfigration file :( change hostnames and ips... when they'll comply, direct them to using pac ;) However, the PAC won't work for HTTP clients not supporting javascript (e.g. wwwoffle) > Assuming a big budget, check out Radware's Cache Server Director: > http://www.radware.com/content/products/csd/default.asp > > So basically we need some sort of load balancing (or a quasi-random > > distribution of the users' request onto the 3 servers) in a way that > > makes sure that a user always uses the same proxy for any given > > destination host (I assume that some net-banking applications get > > suspicious if the same session originates from different source IPs). I don't know about SLB, but our alteon supports hash mode that will direct the same client to the same server, unless one of servers breaks. afaik linux virtual servers support it too. -- Matus UHLAR - fantomas, uhlar@xxxxxxxxxxx ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Windows found: (R)emove, (E)rase, (D)elete
