WAS and SSL
User Greg Minamide (Greg.Minamide@ImageX.com) posted:
In the Microsoft Web Application Stress Tool (aka WAS), SSL should be
disabled by default. However, if you need to disable this manually, you can
go to the main script page (in the right pane, it should read with a series
of columns "Verb", "Path", "Group", "Delay"). Double click the row header
(gray area to the left of any row). You will be taken to a new pate with 5
tabs, SSL being one of them. You'll be able to disable SSL here.
If you're having problems recording scripts using SSL, you'll have to
disable SSL on the server, then record, then enable SSL on the server and in
the tool for successful playback. You can also add SSL pages manually if
The Microsoft WAS Tool is all free. You can find further support at: http://homer.rte.microsoft.com/ or the Microsoft WAS alias at:
Re: WAS and SSL
User Tim Gerrells (email@example.com) posted:
WAST - great tool; fairly well featured. Free. Handles full SSL support. Per
the online help file:
Secure Socket Layer encryption
You can stress test servers that use Secured Socket Layer encryption method.
When scripts are written using the HTTPS protocol, Web Application Stress
interacts with the web server by providing the necessary data for each
To use Secure Socket Layer, do the following:
1. Double-click a script item and select the SSL tab.
2. Click the Use SSL check box.
3. Choose Apply to all if you would like all paths in the script to use
Server-side CPU utilization will be at least 5 times higher when using SSL.
This value was determined using a simple 5 kb ASP file (0.87M cycles to
4.33M cycles per request). The SSL per-byte cost is about 3 times higher on
un-buffered active content compared to static content. Since static content
has a lower base CPU cost than ASP by a couple orders of magnitude, the
overall server-side CPU increase for static content is substantially more
than the 5 times measured for ASP.