The Recorder includes a feature that enables you to filter out specific requests from tests. This filtering occurs as the transaction runs; any objects requested from the filtered object are also filtered.
Object filters are designed so that you can turn filtering on and turn off at any point in the transaction. When turning on a filter, you must provide a list of filter criteria. Each list item contains the following:
- URL fragment – Any substring of the URL(s) to filter. To filter all objects from a specific domain, you can enter that value as the URL fragment. This fragment is matched against the full URL, including the protocol (
- Match criteria – Set to
Starts with, or
Ends with, to specify where to find the URL fragment in relation to the full URL.
You also have the option to set the script to include objects that match the filter list and exclude any requests that do not meet the filter criteria.
All browser agents (Chrome, IE, Firefox, and Mobile) support the Filter action. The action works differently in each browser because of the way the browsers filter objects.
See below for information specific to the IE and Firefox agents.
Object filtering in the IE agent
The IE agent intercepts each outbound request and checks the full URL (including the protocol) to see if it matches any of the filter criteria. It works down the list in sequential order, so if two filters match an object, the match that is furthest up the list catches it.
If the URL matches a filter, the agent does not send the request for that object. Any objects loaded as a result of that request also is not requested.
Object filtering in the Firefox agent
Like the IE agent, the Firefox agent filters objects by blocking the requests before they go out. The Firefox agent, however, takes advantage of a built-in filter policy in the Firefox browser. The filtered objects are added to the policy's filter list, and the policy is called prior to the agent making the object request.