Hi, You understand for that correctly. To resolve this problem, you need a cookie based module for session maintance. For example, Squid will send a cookie to client's browser on the first request. And squid will fetch the cookie when this client access to it. Based on this you will differ each client really and redirect the same client to the same backend server. I have written that a module, but for our private usage only. IIRC, visolve squid will provide that a module for free, try google visolve, good luck with it. Regards. ---------- Original Message ---------- From: NublaII Lists <nublaii.lists@xxxxxxxxx> To: Jeff Peng <jeffpeng@xxxxxxxxxxx> Cc: squid-users@xxxxxxxxxxxxxxx Subject: Re: squid 2.6/2.7 with cache_peer and sourcehash Date: Wed, 25 Nov 2009 12:05:25 +0100 Hi, and thanks for the answer. Yes, we are using it as reverse proxy, but the main concern is about the posibility of getting a huge range of users masked behind a common IP and hammering just 1 server... is that possible or am I understanding the sourcehash mechanism wrong? ____________________________________________________________ Human Resource Training Complete an accredited human resources degree, 100% online. Free info! http://thirdpartyoffers.netzero.net/TGL2231/c?cp=hxrnf_kgK2JykBjhg-Tf0gAAJz4_zcPXSKpk-wtwPtDFgJ8JAAQAAAAFAAAAAEa2Mz4AAAMlAAAAAAAAAAAAAAAAAAASIwAAAAA=
