[OpenSTA-devel] [ opensta-Bugs-1752657 ] Consecutive ~s in recording cause bad SCL or Modeler hang

[SourceForge.net <no...@so...>]

Bugs item #1752657, was opened at 2007-07-12 10:07
Message generated for change (Comment added) made by dansut
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110857&aid=1752657&group_id=10857

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: HTTP Capture
Group: Behavioral
Status: Open
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Daniel Sutcliffe (dansut)
Assigned to: Daniel Sutcliffe (dansut)
Summary: Consecutive ~s in recording cause bad SCL or Modeler hang

Initial Comment:
The symptoms here are that the Modeler will just hang after a recorder is finished (using 100% CPU) or the created script will be missing bits, typically it won't have any of the required variables defined in the Definition section.

The problem is that the Gateway creates a badly formed intermediate recording (TOF) file if the content contains multiple consecutive ~ characters.  This was first noted with a Cookie containing a '~~' sequence, which when encoded for SCL becomes '~~~~', but it is possible that consecutive ~s in many parts of the recorded HTTP stream can cause the same problem.

The same problem can be artificially created by using the Modeler Comment button whilst recording and typing in a string of more than 3 ~s.

----------------------------------------------------------------------

>Comment By: Daniel Sutcliffe (dansut)
Date: 2007-07-17 11:01

Message:
Logged In: YES 
user_id=19748
Originator: YES

A fix for this issue has been merged into the CVS HEAD.  It
will become generally available in the OpenSTA 1.4.4 release.

gwhttp.dll: 1.4.4.5
OpenSTA: 1.4.4.7

This problem was fixed by avoiding the use of the '~~' string
to represent a single '~' when encoding SCL strings.  Instead
the hex representation of ~<7E> is used.  For the issue with
comments the problem strings are simply truncated to the
shortest sequence that does not cause a problem.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110857&aid=1752657&group_id=10857