Disable and enable secondary HTTP requests

You can disable all secondary requests within an HTTP performance test or a subset of requests in the test. Secondary requests are all requests within a page other than the primary request.

To disable other elements in tests or schedules (for any protocol), see Disable portions of a test or schedule.

  1. In the Test Navigator, browse to the test, and double-click it.

  2. In the Test Element Details area, click the HTTP Options tab.

  3. At Secondary request behavior, click Modify.

  4. In the Enable or Disable Secondary Requests box, select one or more of the following options:

    Option Description
    All secondary Selects all secondary requests.
    Images Selects all secondary requests that are image-related. This selection includes all secondary requests where the Content-type header of the response contains image or the path of the URI of the request contains a .gif, .png, .jpg, .bmp. or .tif extension.
    Host/Port based Selects all secondary requests that use the specified host:port pair for connections. A list of host:port pairs in the test is displayed.
    User-defined Selects all secondary requests where the user-specified string, or a string matching a user-specified regular expression, is in the request URI.

  5. You typically keep the boxes under Do not disable secondary requests selected, which leaves them enabled. However, if you have extensive knowledge of the system under test and have already done some troubleshooting, you might clear these boxes in the following cases:

    • With responses containing set-cookie headers: If the cookies set in a particular request are not important to the remaining requests, you may disable them. This decision requires you to know how the system under test uses cookies.
    • With data sources used by enabled requests: If a test contains superfluous data correlation, you may disable it. This decision requires you to know how the system under test uses data correlation.

  6. Select Disable or Enable to modify the secondary requests. The requests are now enabled or disabled.


Related:

Redirection support for HTTP tests
HTTP test editor overview
Cut and paste in tests
Specify the number of allowable URL redirects during test runs
Define performance requirements in tests
Add an authentication folder
Verify expected behavior
Specify error-handling behavior
How loops affect the state of virtual users
Split a test
Split a test page
Merge test pages
Reuse tests on different hosts: Server connection variables
Convert tests to use SSL connections
View a test in the Protocol Data view
Test Siebel applications


Error 404 - Not Found

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.