HTTP parsing rules work on the following basis: During recording, each server response is parsed for rule hits. These are the string values located by the recorder using the search criteria in the HTTP parsing rule which are retained for future use. When the Recorder later attempts scripts a string value, it examines all rule hits and determines a set of script hits, non-overlapping strings that match the rule hits. The Recorder then scripts the necessary parsing functions and variable replacements. There are circumstances where it may be useful to automatically parse a value using a recording rule where there is no occurrences of this value to be replaced in the script. There is an undocumented ScriptGen attribute ForceScripting that forces the scripting of parses without a matching string value in the script. The following example rule shows how to use this attribute: The .xrl file for the above rule is attached to this article. Incident #2505644 Attachments ForceScripting.zip Old KB# 34119
↧