Posted By hoolio on 05/13/2011 01:07 PM
Hi Thomas,
Are you using an iRule to selectively enable the stream profile rewriting? If not, that's the first thing I'd try. You can use an iRule like this:
From: http://devcentral.f5.com/wiki/default.aspx/iRules/stream__expression
Example which replaces http:// with https:// in response content
Prevents server compression in responses
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"}{
Replace http:// with https://
STREAM::expression {@http://@https://@}
Enable the stream filter for this response only
STREAM::enable
}
}
Aaron
We are using that exact iRule, and getting the same issue. We were using a generic "stream" profile instead of an iRule, and changed that on our test VIP today, and still encountered the same problems.
We do have two "trunks" set up, and they have a very high amount of drops on incoming requests. Were not sure if that is related or not, but our switch ports don't have any errors on them, so it appears to just be on the F5 side.