HTTP request details

You can enter a name in the Name field for the HTTP request to identify the request in the Page Element Performance or Page Element Percentile report by using the specified name instead of Universal Resource Locators (URLs).

If you select the Generate unique names for HTTP requests checkbox from the product preferences, then the Name field has a predefined unique name for the HTTP request. You can go to Windows > Preferences > Test > Test Generation > HTTP Test Generation to select or clear Generate unique names for HTTP requests.

After you select Generate unique names for HTTP requests, you can rename the HTTP request if the predefined name does not suit your requirement.

The Version field displays the HTTP version of the page request.

The Method displays the HTTP request method that was used during the recording process. You cannot change this value unless you add a new request to a test. The Method field includes the following options:

• GET

• POST

• PUT

• HEAD

• DELETE

• PATCH

• OPTIONS

The Primary request for page option displays for the primary request, and you cannot be modify it. A page can contain only one primary request.

The Click to set as primary option displays for all secondary requests.

If you select this option, then the Primary request for page option is moved to the selected request, and the Click to set as primary option is moved to the original primary request.

You can specify the connection of the web server in the Connection field. The connection includes the hostname, that is Fully Qualified Domain Name (FQDN), and the listener port on the web server.

You can click the name of the Connection to navigate to the Server Access Configuration Details pane where the connection is defined. You can also click Change to update the connection used for the Request.

The Total number of requests field is applied to HTTP Secondary Request Generator.

You can specify the number of requests to send to the server. If there is an array variable assigned to the Request, the number of requests set in the Test editor takes precedence.

You can specify the path to a resource (such as a page, graphics file, or stylesheet file) in the URL field. When the method is GET, then the URL field includes query strings that are designated as dataset candidates.

You can specify additional content data in the Data field that might be needed to clarify a request. When the method is POST, the data frequently includes values that are designated as dataset candidates.

The Request Headers field lists the header of a request and its value.

You can change the value of the header by clicking the Modify option. You can click Add to add a new header for the request. You can also delete the header for the request by clicking the Remove option.

You can select the Enable response time breakdown option to trigger the collection of response time breakdown data. You can also enable the response time breakdown collection at the parent or page level.

You can select this checkbox to view the URL substitutions in the Page Element Performance and Page Element Percentile reports.

This section displays all the performance and functional requirements in a table. The grayed-out requirements in the table indicate that they are undefined.

You can use the Operator and Value fields to define a requirement.

You can right-click either the Performance or Functional requirement from the table, and then select Copy Requirements to use the defined requirement in multiple requests.

You can select this checkbox to enable the selection of the performance and functional requirements for the test.

You can specify a name for the set of defined requirements in the Name field. The default name is the URL of the request. Although you can change the name to improve readability, only the Requirements report uses this name. Other reports use the default name.

You can also click the Use Defaults option to reset the value of the Name field to the default value.

You can click this field to view the mathematical operators from the list. You can select the operator from the list to define the Performance or Functional requirements.

You can click this field to provide a value for the Performance or Functional requirements.

You can clear this field to disable the requirement to be processed by the report as a standard requirement. The standard requirements can cause a test to fail. The requirements that are not listed as Standard do not cause the test to fail.

You can select this checkbox to hide all the undefined requirement candidates.

You can click Clear to remove the defined requirements. The requirement is still available and can be redefined anytime.

You can use Error Handling to specify an action to take and a message to log when a specific condition occurs. The error conditions in the table include verification point failures, server timeouts, custom code alerts, and data correlation problems. All error conditions are displayed in the table, with action to take and the message to log when the error occurs.

You can select the Condition checkbox from the table to define an error handler. The Errors page in the report lists the number of errors and the corresponding actions that occurred in the test or schedule.

You can select this checkbox to display only the selected error handlers.

This field indicates the data transformation that is applied to the request. You can click Change to select a data transformation to apply to the request.

You can specify pre and post-processors to modify and inspect certain aspects of the action before and after it is executed.

You can click Create to create a Java file that contains the skeleton of the Java file needed for the pre and post-processors. You can also click Browse to navigate to a Java processor that you have already created.

This option indicates the character set to be used for the page request. You can click Change to view and select valid character sets.

This option indicates the associated request that must start or finish before the request is issued. You can click Request to select a different request. You can also click the Clear request association icon to remove the association.

You can select a value from the drop-down list to indicate when the request is issued to the associated request.

This field indicates the additional delay, in milliseconds, to wait before the request is issued. The delays are statistical emulations of user behavior. You can scale this delay at the test level to make a test playback faster (or slower) than the speed of the recording process.

You can specify the time threshold to initiate the action in the Override timeout value field. The test waits up to a specified amount of time for a request. If the request arrives before the timeout limit, the test proceeds to the next action immediately when the request is received.

This field applies to HTTP Secondary Request Generator. You can use the delays to control the flow of requests to the server. You can select a value from the drop-down list in the Release when field to know when exactly to release the request.

For instance, the First Character Sent option indicates to release the second request after the first character in the first request that is sent.

This field lists the details about the certificate stores that the test uses. You can click Add to add a certificate store for the test to use.

The HTTP and SOA protocols support digital certificates. The other protocols do not support digital certificates.