dcgames
asked on
Testing SSL access with MS Web Application Stress tool
We have a web site that we are trying to stress test.
When we access the web site using a web browser, everything seems to run ok.
When we set it up under MS Web Application Stress tool (WAS), SOME of the SLL pages fail.
The pages that fail, do so consistently. Those that work, don't fail.
Using the "session trace" capability and the TCP/IP trace also, the developer states that the TCP/IP trace shows all the data, while the "session trace" seems incomplete.
He also states that the WAS tool pauses upon invoking one of the pages that fails, waits for 2 minutes and then stops.
This all sounds a bit wierd to me, but while I go dig up some more info I wanted to ask if anyone ever used the WAS tool to test SSL enabled applications, and whether there were any issues involved.
According to WAS docs, all you do is select "Use SSL" for the particular page and that's it.
They do have a certificate, and it's valid. They also setup a site with a "temporary certificate" that basicly allows everyone access (no security). Same problem.
Any ideas?
I've put 100 points here, but I'll grant 200 or more for a solid answer that solves our problem..
Dave
When we access the web site using a web browser, everything seems to run ok.
When we set it up under MS Web Application Stress tool (WAS), SOME of the SLL pages fail.
The pages that fail, do so consistently. Those that work, don't fail.
Using the "session trace" capability and the TCP/IP trace also, the developer states that the TCP/IP trace shows all the data, while the "session trace" seems incomplete.
He also states that the WAS tool pauses upon invoking one of the pages that fails, waits for 2 minutes and then stops.
This all sounds a bit wierd to me, but while I go dig up some more info I wanted to ask if anyone ever used the WAS tool to test SSL enabled applications, and whether there were any issues involved.
According to WAS docs, all you do is select "Use SSL" for the particular page and that's it.
They do have a certificate, and it's valid. They also setup a site with a "temporary certificate" that basicly allows everyone access (no security). Same problem.
Any ideas?
I've put 100 points here, but I'll grant 200 or more for a solid answer that solves our problem..
Dave
ASKER
So you couldn't test SSL performance?
Dave
Dave
No...not with this tool.....so just stress tested it by simulating a huge user load....used 50 PC's and a constant refresh....
Sorry I couldn't be more helpfull...
Max.
Sorry I couldn't be more helpfull...
Max.
ASKER
I think we just figured it out. Someone please tell me if this makes sense. We changed the protocol from HTTP 1.1 to HTTP 1.0 and now SSL testing works.
I have no idea why the HTTP setting would affect SSL testing, but that solved the problem.
I'll wait a few days to see if anyone offers some additional insight.
Dave
I have no idea why the HTTP setting would affect SSL testing, but that solved the problem.
I'll wait a few days to see if anyone offers some additional insight.
Dave
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Guess I cannot complain about the C grade as I was not able to tell you a way that it does work....but a C is usually not given....
Anyways...
Glad I was able to help you...if only just a bit...
Max.
Anyways...
Glad I was able to help you...if only just a bit...
Max.
Max.