LTM stream profile: Multiple replacements & regular expressions
LTM's built-in stream profile (and related iRules commands) offer a relatively low-overhead method to replace specific strings in the server response data. One of the most common uses for stream...
Published Sep 12, 2007
Version 1.0
Thanks for the feedback, guys!
- Nicolas: HTTP payload replacement using the HTTP::collect command is much more resource intensive than the stream profile. The collect commands buffer the entire response data set in memory, then some operations may expand up to 4x original size due to internal charset conversions, which may cause memory exhaustion under load and force TMM to restart (as seen in your log snip). Since you mention the iRule was applied to several virtual servers, that is likely what you experienced. Good to hear that the stream profile helped solve the problem
- Aaron: Last time I tested, the stream profile affected only response data. I am checking with Support regarding request data and to find out if there is any version-specific info we should know.
peace
/deb