<< Generator per Protocol tab for HTTP | Correlate variables in response >>

Supplying Variable Data Values to an HTTP Script

Setting Recording Options

6-28

b. Allow cache responses

Allow cache responses

Select this option to enable a script to play back successfully if a response is
cached differently during playback. This generates a script that sets the TSS
environment variable

Http_control

HTTP_CACHE_OK

. Leaving this box

cleared enforces strict interpretation of recorded cache responses during
playback.

Allow redirects

Select this option to enable a script to play back successfully if the script was
directed to another HTTP server during playback or recording. This
generates a script that sets the TSS environment variable

Http_control

HTTP_REDIRECT_OK

. Leaving this box cleared enforces strict

interpretation of recorded redirects during playback.

d. Use HTTP keep-alives for connections in a session with multiple scripts.

Generally, leave this box cleared.

Selecting this option provides more accurate representation of keep-alive
behavior, but at a cost--if you loop scripts or play them back in a different
order, you must manually edit your scripts to achieve successful playback.

Therefore, select this option only if:

You will not loop scripts or play them back in a different order (or, if you

do, you do not mind editing the scripts).

You want to preserve the browser's keep-alive behavior that is in the

recorded session.

For multiple script recordings it is best not to use keep-alives. This prevents you
from having to be aware of persistent HTTP connections that span script
boundaries when you loop or change script ordering. However, the default
behavior may result in increased HTTP server overhead due to the absence of
keep-alives.

Supplying Variable Data Values to an HTTP Script

Dynamic data correlation is a technique to supply variable data values to a script
when the transactions in a script depend on values supplied from the server.

When you record an HTTP script, the Web server may return a unique string, or
session ID, to your browser. The next time your browser makes a request, it must
send back the same session ID to authenticate itself with the server.

The session ID can be stored in three places:

In the

field of the HTTP header.