On Tue, Nov 4, 2014 at 7:36 PM, Rajalakshmi Iyer wrote:
> Ok. Thanks.
>
> Does this situation sound plausible - Keep alive connections are not being
> used effectively by client applications (i.e. subsequent requests on
> keep-alive connections are not frequent enough to keep Apache workers busy
>
I’ve just finished creating a script that will test my app for content and
functionality.
I use WWW::Mechanize and Test::WWW::Mechanize
Getting their nuances took me some trial and error, There are some thing it is
missing, su as proof that a radio button was actually clicked
Or I havn’t figured
On Thu, Nov 6, 2014 at 2:37 PM, Rose, John B wrote:
> Any pro/con views, personal experience, insights on these tools, or any
> not listed here you think are good?
>
> Ab - Apache
> jmeter
> Webpagetest
> Httperf
> Apache Flood
>
> We have tried ab, webpagetest, and jmeter a bit but still lear
What about the Includes?
On 11/06/2014 10:14 PM, Steve Matzura wrote:
> It occurred to me that apache2.conf might be what's wanted. Here it
> is, without the comments, and lots of white space removed.
>
> ServerRoot "/etc/apache2"
> LockFile /var/lock/apache2/accept.lock
> PidFile ${APACHE_PID_FILE
Try Burp (not free paid version)
URL : http://portswigger.net/burp/
It is good for http/https/rest/soap . testing
with regards
karthik
On Fri, Nov 7, 2014 at 1:07 AM, Rose, John B wrote:
> Any pro/con views, personal experience, insights on these tools, or any
> not listed here you
