If I may add, a redirect logic may not work in some cases. If you let unmodified HTML content through to the client with HTTP:// references, and then generate a redirect to HTTPS:// for every request to a separately maintained VIP, you have at least two problems:
-
As stated, you have to maintain two VIPs,
-
But most important, for every one object in the HTML you're potentially generating two round trips (if not more). It may be less load on the F5, but it'll definitely slow the client down.
The beauty of the STREAM filter is that it actually processes traffic (as a stream) within TMM, which is pretty darn fast. In comparison to a generic string manipulation routine that has to first buffer the payload before writing to it, a STREAM filter is generally way more efficient.
If you're still worried about performance, try adding the timing option to your event declarations and test with and without the STREAM filter.