Forum Discussion
jvuong004_98902
Oct 14, 2011Nimbostratus
Thanks for the response. Actually, the delimiter can be set to a number of items. It just depends on what you decide upon. I was using the @ sign at first but since I was appending domain names that have @domain.com it was not parsing out correctly. Please note that the STREAM::expression line does work and does match. I have it logging out and it works just fine. I have alternate code that runs my replacements just fine. Alternate code is below: .*/-:_?=@,& (period, asterisk, forward slash, dash, colon, underscore, question mark, equals, at, comma, ampersand)"
Behavior of below code:
----------------------------
Input: LOGIN "username" "password"
Output: LOGIN "username@domain.com" "password"
-------------------------
when CLIENT_ACCEPTED {
STREAM::expression {:\" \":@domain.com" ":}
STREAM::enable
}
when STREAM_MATCHED {
log local0. "Stream filter matched: [STREAM::match]"
}
****************************************
Reference Article for using alternate delimiters:
****************************************
http://devcentral.f5.com/Tutorials/...sions.aspx
Quote:
"The first character in the field () defines the delimiter bounding each field for this replacement, and must not appear anywhere else in the target string. can be any one of the following characters: