In some cases the function WebCookieSet may be recorded where this is not useful or even incorrect.
This may happen when there is a tight succession of client side "Cookie" and server side "Set-Cookie" headers in embedded objects of a page, with tight timing. In such a case it is possible that a browser does not send a cookie or sends a cookie with an older value, although the browser already received a "Set-Cookie" header which should cause it to send a different cookie value.
In such cases, these actions can be used to script WebCookieSet function calls commented or suppress the recording completely.
This rule suppresses scripting of any WebCookieSet function call if the cookie name is PS_TOKENEXPIRE (from the Peoplesoft SilkEssential).
<HttpScriptingRule> <Name>Suppress Cookie PS_TOKENEXPIRE</Name> <Active>true</Active> <Action>SuppressCookie</Action> <Conditions> <CompareData> <ApplyTo>Cookie</ApplyTo> <Data>PS_TOKENEXPIRE</Data> </CompareData> </Conditions> </HttpScriptingRule>