Add Ip member pool in my header browser

That's very odd. I'm not sure what would cause the error. I'd suggest opening a case with F5's support group about this.

 

 

Here are a few questions I'd be curious about:

 

 

With no changes to the iRule, if you disable all but one member in the pool, you never see the error? But as soon as you add a second member you see the error? With multiple pool members, does the error occur on every single response that the stream filter is enabled on?

 

 

Aaron