[prev in list] [next in list] [prev in thread] [next in thread] 

List:       grinder-use
Subject:    Re: [Grinder-use] extracting inputs from response body
From:       Philip Aston <philipa () mail ! com>
Date:       2013-02-26 18:09:56
Message-ID: 512CFA74.7090207 () mail ! com
[Download RAW message or body]

The TCPProxy ought to have recorded the HTTP requests that return the
blob. You can get at the response body in text form (response.text) or
binary form (response.data).

- Phil

On 14/02/13 22:46, Bill Smith wrote:
> In the webapp I'm testing, there used to be pages with hidden inputs
> that were posted in subsequent HTTP requests.  Of course, Grinder
> deals with that; the valueFromHiddenInput method on the HTTPUtilities
> interface will return the value of a hidden input.
>
> In the latest version of the webapp, some of those inputs are now
> values in a JSON blob embedded in a <script> element.  A Javascript
> callback (or something) fills those values into the page once the page
> is loaded.  
>
> I need some of those values to construct subsequent HTTP requests, so
> I am trying to figure out how I can extract them from an HTTP
> response.  Is there a hook in Grinder that I can use to extract
> additional information from the payload of an HTTP response?
> (I'm currently using Grinder 3.8 because that's what was current when
> I last touched this code last spring.  However, I can use a newer
> version if it helps to do so.)
>
> Thanks,
> Bill Smith
> Austin, TX
>


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
grinder-use mailing list
grinder-use@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/grinder-use
[prev in list] [next in list] [prev in thread] [next in thread]