Can anybody tell me why source-hash algorithm in cache_peer directive can't handle the session case? Since source-hash (if I understand for it correctly) will redirect users' requests based on their IPs, so the same IP will always go to the same original server. That will keep session always valid. Thank you. 2008/6/13 Ken W. <kenw97@xxxxxxxxx>: > Thanks Henrik. > Can source-hash algorithm in cache_peer handle this case? > since source-hash is based on users' IP for redirection. > Thanks again. > > > 2008/6/12 Henrik Nordstrom <henrik@xxxxxxxxxxxxxxxxxxx>: >> On tor, 2008-06-12 at 18:13 +0800, Ken W. wrote: >>> I have two original servers behind Squid boxes. >>> How to keep requests from the same client always going to the same >>> original server? >> >> the srchash selection mechanism is intended for this, routing requests >> with the same source IP to the same server. >> >> It's also possibe to do it based on some server-unque property of the >> session cookies issued by your server by using the req_header in >> cache_peer_access. Just make sure the session cookie is temporary or >> failover situations when one of the servers is down gets a bit tricky.. >>
