Stream Profile - Sample?

Hi Greg -

 

 

I don't think I can answer all of your questions, but here's what I know:

 

 

1)

 

Defining the replacement pairs in the target string is correct for multiple replacements, however, your syntax is a bit off. It should include delimiters around source and target for each replacement pair, resulting in /2/ delimiters (plus optional whitespace) between each replacement pair, so the correct target expression would be:

 

@abc@xyz@ @123@456@

 

or

 

@abc@xyz@@123@456@

 

 

2)

 

Stream profile will operate against all returned content, but not headers. (Header/data boundary determined by protocol profiles applied to the virtual server.)

 

 

3)

 

Binary data would not be decoded, but if by chance the bytestream matched, a replacement would be performed.

 

 

4)

 

Yes, the stream profile is case sensitive, and as far as I know there is no way to modify that.

 

 

I hadn't encountered the 4MB limit you mention -- was that info provided by F5?

 

 

And one more thing: It sounds like you are using both the stream profile and other iRule functions to replace the payload. I'm not sure how the "collect/release" functions interact with the "stream" functions, but they do operate in different paradigms and some incompatibility between the 2 approaches is possible.

 

 

HTH

 

/deb