iRule command value caching?

Hi,

 

 

Could someone provide more detail on caching of command values in iRules (example: you modify the URI with HTTP::uri and then try to log the modified value).

 

 

Is it feasible to get a list of the commands which are cached? If not, is there criteria you can provide for what types of command values are cached?

 

 

When a command is cached, it seems like the initial value is current but all subsequent references to the command are cached (at least within the same rule event). Is there anything that triggers updating of the cached value? Is the cached value shared between two different rules on the same TCP connection if both rules are associated with the VIP? It looks like the cached value is not shared. If there are two events in the same rule at different priorities, is the cached value shared? It looks like it's not.

 

 

I'm mostly interesting in the HTTP:: commands--particularly the HTTP::cookie and HTTP::header values. I'm testing on 9.2.4. Has the command caching changed in more recent versions?

 

 

I understand that the caching saves resources and is probably built in at a low level, but is there an option of disabling the caching (perhaps on a test unit)? It is complicating some troubleshooting.

 

 

Thanks for any info you can provide,

 

Aaron