curl-loader-devel

[curl-loader-devel] Page being posted to?

[Jeremy H. <je...@no...>]

Run-Time,Appl,Clients,Req,2xx,3xx,4xx,5xx,Err,Delay,Delay-2xx,Thr-In,Thr-Ou=
t
0, Appl, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
0, Sec-Appl, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
*, *, *, *, *, *, *, *, *, *, *, *, *
Run-Time,Appl,Clients,Req,2xx,3xx,4xx,5xx,Err,Delay,Delay-2xx,Thr-In,Thr-Ou=
t
1, Appl, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
1, Sec-Appl, 0, 7, 2, 5, 0, 0, 0, 35, 3, 38088, 3202

Re: [curl-loader-devel] Page being posted to?

[Robert I. <cor...@gm...>]

On 5/17/07, Jeremy Hicks <je...@no...> wrote:
>
> Is there any way to see the actual data being received/sent for the
> requests (e.g. the html of the pages)?
>


Correcting myself. option -o may not to be working any more.

 However, all the HTTP body bytes passed are seen by the function
 do_nothing_write_func in loader.c, which just skips the bytes.
 As a temporary workaround you can place inside the function:
--------------------------------------------------------------------------
static FILE* myfile = fopen ("myfile.txt", "w+");
fwrite(ptr, size, nmemb, myfile);
return(nmemb*size);
---------------------------------------------------------------------------
It should work for a single transfer, whereas a solid solution to be
as described in our TODO list.

Another option in meanwhile to see the body bytes of the
non-encrypted responses is using ethereal/wireshark sniffer.

-- 
Sincerely,
Robert Iakobashvili,
coroberti %x40 gmail %x2e com
...........................................................
http://curl-loader.sourceforge.net
A web testing and traffic generation tool.

Re: [curl-loader-devel] Page being posted to?

[Robert I. <cor...@gm...>]

On 5/17/07, Jeremy Hicks <je...@no...> wrote:
>
> Is there any way to see the actual data being received/sent for the
> requests (e.g. the html of the pages)?
>

The good news is that I have added initial support for that to svn.
Y may try it for a not more than several clients and a few cycles.

Please, add the new tags described below to the login_new.conf
file, which I sent you before.
Please, note, that the tags are per url, therefore, you may wish
to add them both to you GET-url as well as the POST-url section
(no actual url, just posting to the url fetched by GET and 3xx-es).

>From the Changelog
------------------------------------------------------------------------------------
* Added an option to log response body-bytes and headers to
   files. To log body bytes add tag LOG_RESP_BODIES=1 to your
   configuration file. To log headers add LOG_RESP_HEADERS=1.
   See log_hdr_body.conf as an example.

   Directory <batch-name> is created with subdirs url0, url1, url<n>
   Each url subdir contains files named
   cl-<client-num>-cycle-<cycle-num>.body or
   cl-<client-num>-cycle-<cycle-num>.hdr respectively.

   Note, that output to file is currenly done in a most simple way
   and seriously impacts performance. Use it only with a small number
   of clients and for a few cycles.
----------------------------------------------------------------------------

Thank you.

Sincerely,
Robert Iakobashvili,
coroberti %x40 gmail %x2e com
...........................................................
http://curl-loader.sourceforge.net
A web testing and traffic generation tool.