scrub out going traffic.

Could you post the tags again? This is probably something you'd want to use a STREAM profile for, but let's have a look to be sure.

Hi Jay,

 

 

The forums will scrub text between two angle brackets. Can you put the content in [ code ] [/ code ] blocks?

 

 

In general, you can use a blank stream profile, an iRule which uses STREAM::expression to remove the content and a custom HTTP profile with response chunking set to rechunk to do this:

 

 

http://devcentral.f5.com/wiki/default.aspx/iRules/stream__expression

 

 

Aaron

Here it is.

 
 ............ 

Thanks,

...

So you could set the string expression to something like this:

STREAM::expression {@[^<]+@@}

And use that in an iRule:

when HTTP_REQUEST {
    Disable the stream filter for all requests
   STREAM::disable
}
when HTTP_RESPONSE {

    Check if response type is text
   if {[HTTP::header value Content-Type] contains "text"}{

      STREAM::expression {@[^<]+@@}

       Enable the stream filter for this response only
      STREAM::enable
   }
}

Aaron

Thanks Aaron,

 

 

I will try that.

Hi,

Can you please help me with how I am suppose to setup the stream profile ?

you mentioned :

 STREAM::expression {@[^<]+@@} 

When I go to create the stream profile, it has options for source and target, I am not sure I understand what I should use for source / target in the profile.

Thanks for your help.

Jay, you don't need to put anything in the stream profile with this iRule, you just need to make sure a stream profile is attached to the VS when the iRule is added to it. The iRule is actually switching on the stream replacement when it gets content of type "text" and setting the expression it is going to use... all you need to do is enable a (blank) stream profile on the VS.

Academic question here - why not just apply the target/replace strings into a STREAM profile on the virtual? If it's a simple enough expression, I'm not sure what's gained by using an iRule here. Just curious.

 

 

(I know, HERESY. :) )

You can do that, sure. The iRule approach is a little better because it will allow you to precisely target specific content-types with the Stream match, and not apply to all content by default. Saves CPU and -- most importantly -- administrator brain cells when an overmatch occurs and they're forced to troubleshoot it. :>