Re: Additional features with patch included

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

Hi François,

On Mon, Mar 23, 2009 at 5:07 PM, François <fra...@gm...> wrote:

> Hi,
>
> I am working on a SaaS product based on a HTTP proxy developed from
> scratch.
> In order to test it correctly, last year, I have submitted a bug fix
> related to the proxy authentication mechanism.
> Now, the QA team of my company needs two additional features in
> curl-loader:
> 1-      The cookies must be managed per proxy-user, in order to simulate a
> more “realistic” traffic.
> For the following configuration:
> BATCH_NAME=get_post_login
> CLIENTS_NUM_MAX = 1
> INTERFACE=lo
> NETMASK=24
> IP_ADDR_MIN=127.0.0.1
> IP_ADDR_MAX=127.0.0.1
> CYCLES_NUM= 1
> URLS_NUM=3
> ### Set a cookie for user test1
> URL= http://www.example.com/cgi-bin/set-cookie?cookie=cookie_for_user1
> PROXY_AUTH_METHOD=<http://www.example.com/cgi-bin/set-cookie?cookie=cookie_for_user1%0APROXY_AUTH_METHOD=>
> "BASIC"
> PROXY_AUTH_CREDENTIALS=test1:test1
> URL_SHORT_NAME=" SETCOOKIE1"
> URL_DONT_CYCLE = 1
> REQUEST_TYPE=GET
> TIMER_URL_COMPLETION = 0
> TIMER_AFTER_URL_SLEEP =0
> ### Set a cookie for user test2
> URL= http://www.example.com/cgi-bin/set-cookie?cookie=cookie_for_user2
> PROXY_AUTH_METHOD=<http://www.example.com/cgi-bin/set-cookie?cookie=cookie_for_user2%0APROXY_AUTH_METHOD=>
> "BASIC"
> PROXY_AUTH_CREDENTIALS=test2:test2
> URL_SHORT_NAME="SETCOOKIE2"
> URL_DONT_CYCLE = 1
> REQUEST_TYPE=GET
> TIMER_URL_COMPLETION = 0
> TIMER_AFTER_URL_SLEEP =0
> ### Must replay cookies for user test1
> URL= http://www.example.com/
> PROXY_AUTH_METHOD= <http://www.example.com/%0APROXY_AUTH_METHOD=>"BASIC"
> PROXY_AUTH_CREDENTIALS=test1:test1
> URL_SHORT_NAME="GETCOOKIE1"
> URL_DONT_CYCLE = 1
> REQUEST_TYPE=GET
> TIMER_URL_COMPLETION = 0
> TIMER_AFTER_URL_SLEEP =0
>
> Current curl-loader behavior is to replace cookie of the user test1
> with cookies of the user test2.
> Expected behavior is to have cookies of user test1 marked as different
> from those of user test2.
>
> 2-      A CSV output similar to the “siege” tools, in order to make
> curl-loader output parsed with same script tools.
> The expected behavior is to have a new parameter added to the
> curl-loader command line (-a), that will trigger a csv output  to the
> .log file of the following format:
> get_post_login.SETCOOKIE1.proxyauth=test1,HTTP/1.1,200,0.081726,28,
> http://www.example.com/cgi-bin/set-cookie?cookie=cookie_for_user1,,2009-03-23
> 10:08:24
> get_post_login.SETCOOKIE2.proxyauth=test2,HTTP/1.1,200,0.009584,28,
> http://www.example.com/cgi-bin/set-cookie?cookie=cookie_for_user2,,2009-03-23
> 10:08:24
> get_post_login.GETCOOKIE1.proxyauth=test1,HTTP/1.1,200,0.020465,44,
> http://www.example.com/,,2009-03-23
> 10:08:24
>
> csv format is of the following form:
> test_name,HTTP version,HTTP
> status,total_time,recv_bytes,url,,formatted_time
>
> Feel free to include these modifications to curl-loader if you find them
> useful.
>
> Regards,
>
> *Francois Pesce*
>

Nice hearing from you. How are you doing?

First subject seems to be a rather common matter, whereas logging format
could be a matter of taste.

Could you, please, send to me a patch dedicated to the cookies collection?
Thank you.

-- 
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
www.ghotit.com
Assistive technology that understands you
......................................................................