Forum Discussion
Nov 25, 2008
I'll start with the easy question first - how to send a no-cache header in the response so the client does not cache the item. This is controlled from within the policy's lifetime settings. The last section is the client cache settings there are options for do not change which will pass on the settings from the origin server, maximum age where you can specify a lifetime, and Insert no-cache directive which will instruct the client not to cache.
WebAccelerator currently sets all of it's caching rules based on the request not on the response so preventing the caching of a response is not an easy feat in fact it may not be possible. I'll check around to see if this is possible but chances are it isn't.
Finally the sys_WA_ramcache_clientside rule should not be edited unless explicitly told to do so from F5 support. Making changes to this will likely void your support contract.