[OpenSTA-devel] [ opensta-Bugs-751953 ] Cookie variable size not matched to size of cookies recorded

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

Bugs item #751953, was opened at 2003-06-10 09:43
Message generated for change (Comment added) made by dragonfyre13
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110857&aid=751953&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: Inconvenience
Status: Open
Resolution: None
Priority: 3
Private: No
Submitted By: James Ward (jmrward)
Assigned to: Daniel Sutcliffe (dansut)
Summary: Cookie variable size not matched to size of cookies recorded

Initial Comment:
Cookies that end with "==" lose these characters when 
saved in a cookie variable.  An example from a replayed 
script is below:

1-1 :[525]:HTTPRESPONSE(18): Setting COOKIE_18_1 
to 'SMSESSION=ig/.....sVZgQ=='
1-1 :[529]:LOG: cookie_18_1: SMSESSION=ig/.....sVZgQ


Could possibly happen with other trailing characters in 
cookies.

workaround:  manually add +"==" after any cookie that 
is supposed to have these characters

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

Comment By: Tim Alexander (dragonfyre13)
Date: 2007-10-25 09:18

Message:
Logged In: YES 
user_id=916501
Originator: NO

I'll second this, and as I had a bit of trouble understanding the bug
report, I will put in a bit of clarification from my perspective.

The specific Characters above are not relevant, the length of the Char
array is. As it is now, it simply defaults to 1024. However, this is not
long enough to handle some cookies (one of mine is almost 3000 chars long)
This is quite frustrating, as there is no error, or warning, or anything
when it truncates a char field. I would propose this as the solution.

I originally had the thought to dynamically resize the cookie Char length
when recording it, but as said previously, there is no way to ensure that
the cookie will not be a different, larger size next time. This also adds a
degree of complexity to what is now a simple process. I believe that
logging on truncation is a much cleaner, and much more stable fix for the
issue.

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

Comment By: Daniel Sutcliffe (dansut)
Date: 2003-06-25 07:35

Message:
Logged In: YES 
user_id=19748

Thanks for investigating your issue and finding the root
cause of your propblem.  In future discussing issues like
this on the OpenSTA users mailing list first is likely to
find you quicker solutions and allow accurate bug
descriptions first time:
  http://lists.sf.net/lists/listinfo/opensta-users

I'm not sure there can ever be a perfect answer to this
problem though; yes we should make sure the variables are
big enough to store the cookies recorded but whose to say
that the runtime cookies won't be bigger still.  Perhaps we
also need some sort of warning generated when filling vars
truncates the content as well.

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

Comment By: James Ward (jmrward)
Date: 2003-06-13 11:37

Message:
Logged In: YES 
user_id=798053

I figured this one out myself.  The cookies were not being 
generated incorrectly.  However, the default cookies that the 
script was declaring were not quite large enough.  I realized 
that the cookie I was having trouble with was 1026 
characters long while the automatic cookies were declared as 
1024 characters long (cutting off the last two characters, 
which in this case was "==").  So, the real issue is that 
automatic cookie generation does not dynamically size the 
cookies used, which is just inconvenient.

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

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