On mån, 2008-05-12 at 13:52 +0200, Jan-Frode Myklebust wrote: > Thanks for the pointer, but that's not what we're trying to do no. It's > a webserver cluster, with shared filesystem (GPFS), and heartbeath > (linux-ha.org) for failover ip-addresses which are distributed trough > rr-dns. So, no squid on our side, but the users might be going trough > proxies, so it's important to test that everything works there too. If you have all that, why does it at all matter which server the request got sent to? > Turned out that our problem with browser looping over elements in the > webpage happens if a user is autenticated on the webpage, and switches > from proxied to non-proxied, or non-proxied to proxied connection. So I > guess it's a problem with the php-sessions maybe incorporating the > client ip-address in some cookies, and getting confused if the client ip > changes. So it was not a problem with squid in any way. That's a quite common problem for most session cookie systems. By default they encode the client IP in the session in a weak attempt to try to protect the cookie from session theft. Regards Henrik
