Forum Discussion
NimbostratusHow does the LTM cache my site and how do I flush it?
I've published a website through my LTM v11.3 using a slightly modified version of the f5.http_clientssl iApp.
Shortly after, I noticed one of the static pages had an incorrect CSS file reference and amended it on the backend server. The change has not been reflected when accessing the site via the virtual server. I've tried reconfiguring the iApp, but that doesn't seem to have flushed the cache. I can't see any other obvious method for clearing the cache via the LTM GUI. The iApp has generated a 10MB 'caching profile' with the 'optimized-caching' parent profile.
For the record, I've verified it's not caching the page in my browser by trying it on several machines with several browsers. The page is responding with the amendments when I access it directly via the backend server.
We don't have any other applicable modules enabled that I can see, in particular Web Accelerator is unavailable. I tried the following from the terminal and got a response that it's not provisioned...
wa_clear_cache
WAM needs to be provisioned to clear the cache.
Oddly, if I access the site via the virtual server IP address in my browser, the amendments come through.
12 Replies
Sam_HallMy only feedback on this would be if the cache profile is recreated (as in the case of reconfiguring the iApp that generated it), what ever was in the cache should be flushed. It does seem odd that it persists through a iApp reconfigure. My understanding of reconfiguring an iApp is that all of the configuration elements are torn down and recreated.
- Kevin_Stewart
Employee
I think it's safe to say that the objects within an iApp CAN be deleted and recreated - but that they normally aren't.
