Action notes

  • For ReqSet and ReqAppend the value to set or append can be specified a couple different ways. You can either use a literal string by setting ReplaceString to the required text, or you can pull data from the request or response by using Section, Field, ValueName, StartPattern, StartPatternRE, EndPattern and/or EndPatternRE.
  • When you useg StartPattern or StartPatternRE with one of these actions the RepeatCount is always set to 1 (the first match is always used).
  • IgnoreSpecial is always True for these actions when Section is specified. There is no special handling for the urlfield or cookies sections with these actions.
  • The value for a field (name/value pair) can be cleared without removing the entire field by using ReplaceString with no value: 
    
ReplaceString=
  • All carriage-returns and linefeeds in the value string are replaced with \r and \n.
  • Privacy changes are queued and applied after all actions are complete. This means that actions normally see the original data. ReqSet, ReqAppend and ReqDelete keep track of field additions, changes, and deletions, so multiple changes to a single field (such adding a field then concatenating addition data to the value) can be done safely. Since the Replace action can affect any arbitrary piece of data in the request or response, it is not included in this change tracking. Changes that are made to field values are best done by using ReqSet and ReqAppend.
  • When you use use Field or ValueName with ReqSet or ReqAppend you must specify a single field or value name. If there are multiple names the value for the last item that found is used.
  • Similar to the note above, you must avoid specifying only a section to retrieve the value for a ReqSet or ReqAppend. Doing so results in the value from the last field (name/value pair) in the section that is used for the ReqSet or ReqAppend.