[ grinder-Bugs-3517593 ] recording script in 3.9 beta produced an invalid script

SourceForge.net <[email protected]> Tue, 18 Sep 2012 14:56:48 -0700
Newsgroups gmane.comp.java.grinder.devel
Message-ID <[email protected]>
Bugs item #3517593, was opened at 2012-04-13 15:47
Message generated for change (Settings changed) made by philipa
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3517593&group_id=18598

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: TCPProxy
Group: None
>Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: greghmerrill ()
Assigned to: Philip Aston (philipa)
Summary: recording script in 3.9 beta produced an invalid script

Initial Comment:
The 3.9 TCPProxy does a much better job of creating valid scripts against HTTPS than 3.8.  However, it generated a syntactically invalid script for me.  (See attached.)

The error is:

     [java] net.grinder.scriptengine.jython.JythonScriptExecutionException: <type 'exceptions.TypeError'>: createRequest() takes exactly 3 arguments (2 given)
     [java] 	request501 = createRequest(Test(501, 'POST signon.sso'), url1)
     [java] 	File "C:\views\sso_test\apps\SSOTest\.\wks-gmerrill2-file-store\current\script.py", line 63, in <module>

The offending line is:

     request501 = createRequest(Test(501, 'POST signon.sso'), url1)

Seems for that request it doesn't produce or reference a headers list.  Perhaps not coincidentally, this is the only POST in my script.


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

Comment By: Philip Aston (philipa)
Date: 2012-05-06 08:53

Message:
"Fixed for next release" means committed to my local repo, but not
necessarily pushed to sourceforge :-)

I've just done a push, so you can pick this up now.

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

Comment By: greghmerrill ()
Date: 2012-04-18 07:50

Message:
"Fixed for next release" = already committed?  I tried building from git,
but the problem still persists.  

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

Comment By: Philip Aston (philipa)
Date: 2012-04-14 06:15

Message:
Fixed for next release. Thanks for the report.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3517593&group_id=18598

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/