Forum Discussion
hooleylist
Nov 24, 2008Cirrostratus
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