For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

zafer's avatar
zafer
Icon for Nimbostratus rankNimbostratus
Oct 09, 2008

cache rule for different age and uri

Hello     here is my code     when HTTP_REQUEST {   if { [ matchclass [HTTP::path] ends_with $::cache_obj] or [ matchclass [HTTP::path] ends_with $::images] } {   ...
application delivery
dev
devops
iRules
hoolio's avatar
hoolio
Icon for Cirrostratus rankCirrostratus
Oct 09, 2008
Hi Zafer,

 

 

You can check the cache wiki page (Click here) for details on the commands. It looks like you can get the age of the cached object using CACHE::age. You can expire a cached object using CACHE::expire. You can view the cached objects from the command line using 'b profile http HTTP_PROFILE_NAME ramcache entry all show'.

 

 

I ran into a bug on 9.4.5HF2 when explicitly enabling caching in the HTTP_REQUEST event of an iRule. If the request doesn't contain a host header and the request matches the test to explicitly force caching with CACHE::enable, TMM will crash. F5 noted this in CR108998. The workaround is to either check for a host header, or more ideally, let the caching be enabled in the HTTP profile and then selectively disable it when your caching criteria isn't met.

 

 

Aaron