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
Additional comment..... In the hints and tricks we speak of removing the Accept-Encoding header from the client request to prevent the backend server from compressing the content and making it invisible to the stream profile. Having done this and them attempting to get the BIG-IP to compres the data towards the client with COMPRESS::enable does not seem to work. If I eat the frontend Accept-Encoding I can not seem to get the BIG-IP compression profile to work. Can we post an example of 1) removing the client Accept-Encoding header, 2) stream replacement, 3) COMPRESS::enable for compression towards the client.. showing all three working at once. I could not get this to work.