Nimbostratus
Nimbostratus
When you enable RAM Cache on an HTTP Profile, it works in combination with an iRule (usually), so that you can enable / disable inclusion based on whatever criteria you configure. If you do not control it with an iRule it will cache virtually everything by default.
I would suggest including an iRule that first does CACHE::disable and then does some type of inspection to determine when to enable / include things into it.
Something like this:
when HTTP_REQUEST {
CACHE::disable
if { [string tolower [HTTP::uri]] contains "image" } {
CACHE::enable
}
}
On a side note, you can see what is in RAM Cache from the command line (make sure you are in the correct Partition to run this):
Show all HTTP Profiles (in the Partition you are in) that utilize ramcache.
b profile http all ramcache show
This command will override the default amount of entries dumped from the ramcache.
b profile http (http.profile.name) ramcache entry max response 10000 show
Hope this helps.