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

rb1980_75708's avatar
rb1980_75708
Icon for Nimbostratus rankNimbostratus
Nov 21, 2008

not caching on stream_matched problem

I have an interesting problem I'm hoping can be solved with an iRule:   I have a cgi that proxies to a back-end verity cluster to retreive search results. Occasionally, (because of a problem on t...
application delivery
performance
wa
hoolio's avatar
hoolio
Icon for Cirrostratus rankCirrostratus
Nov 24, 2008
Hi RB,

 

 

I'm not sure how you could disable WAM caching on a response. Assuming you can, I think you'd need to collect the payload using HTTP::collect in order to disable caching as the stream match event might be triggered after the response is already being transmitted to the client. Spark described this in a related post

 

 

 

http://devcentral.f5.com/Default.aspx?tabid=53&view=topic&postid=18766&ptarget=18887

 

 

Since the stream profile is designed to do minimal buffering of server response data, it's quite possible that the client would already have gotten part of the server response by the time the STREAM_MATCHED event fired.

 

 

 

 

Maybe someone else can explain whether it's possible to/how you'd disable WAM caching in the response. You might take a look at the _sys_WA_ramcache_clientside rule in the /config/profile_base.conf file to see what the TMM-WAM rule is doing.

 

 

Aaron