*Note: While this rule is still technically correct, and can provide needed functionality in certain cases, we strongly recommend the use of the Stream profile now available on LTM as it provides ...
It would make sense to restrict the collection to specific request filetypes ([HTTP::path] ends_with ".asp") or to check the response Content-Type header to make sure you don't bother collecting binary content.
Another significant benefit of using a STREAM::expression is you don't have to restrict the server side connection to HTTP 1.0.