Stripping chromeframe from User-Agent

Kevin,

That seemed to work mostly. Now, I'm seeing this in the logs:

Pre-rule:

Jul 17 13:48:17 slot1/tmm info tmm[6849]: Rule /Common/chromeframe_strip : Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; chromeframe/26.0.1410.64; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3; MS-RTC LM 8; .NET CLR 1.1.4322)

Post-rule:

Jul 17 13:48:17 slot1/tmm info tmm[6849]: Rule /Common/chromeframe_strip : Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3; MS-RTC LM 8; .NET CLR 1.1.4322)

Which clearly shows that the User-Agent is having the "chromeframe" information whacked. However, when I monitor via HTTPWatch, I'm still seeing the "chromeframe" information:

User-Agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; chromeframe/26.0.1410.64; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3; MS-RTC LM 8)

Here's the most current version of the iRule:

when HTTP_REQUEST {

set useragent [HTTP::header value User-Agent]

if {$useragent contains "chromeframe"} {

log local0. $useragent

HTTP::header replace User-Agent [string map -nocase {"chromeframe/26.0.1410.64;" ""} $useragent]

log local0. [HTTP::header User-Agent]

}

}