I'm currently tring to use the Beta 22's Recorded Scenario or the "all-in-
one" script recorded by the tcpProxy and the newHttpPlugin. I have NVPairs in
my script that are used to formulate a URL String. One extremely important
NVPair contains multiple 'at' symbols or the "@". This is getting encoded to %
40 when the script executes and it causes the script to crash. I've tried
using the Grinders Decoder class and the actual java Decoder but nothing has
worked. Something in the grinder is decoding this value. When I run through
the process manually and use TCP TRACE, I see that the URL String that is
created contains the @ symbol instead of %40. When I try to execute the
script I created the @ symbol gets encoded to %40 and the script crashes. I
can see all this happening through TCP Trace which by the way is an
invaluable tool when creating scripts.
How can I stop the decoding from happening?