On 26 Jan 2009, at 20:27, Matt Pitts wrote:
If it is Apache, I imagine it's related to mod_cache, although I
*thought* I had it properly configured.
As an exercise; after a simple restart of Apache on the proxy I was
*unable* to duplicate the cookie issue after ten minutes of trying
whereas this morning I had been able to do it after just a few
refreshes.
Has anyone experienced good/bad things with Apache as a frontend
proxy/balancer/cache?
I've seen mention of Varnish on this list as a good frontend proxy.
Any
personal recommendations of it or others?
If you're app isn't sending appropriate cache headers, then you're
stuffed whatever you're using - I don't think that changing the cache
is going to help here - the default varnish config won't cache things
with a cookie, but that still won't help you for users who may be
behind a proxy/cache themselves..
You need to fix the cache headers your app is sending, this is the
only correct solution.
Cheers
t0m
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/