I had created a script to run ask for a couple CLI arguements and then run httperf against a server. The goal was to load test a server for HTTP and for HTTPS. I added the –ssl switch but could not verify a couple things including if httperf had been compiled with SSL support or if the –ssl was working at all.
1. Was httperf installed with SSL support?
This is an easy one. If the –ssl option exists then your httperf was compiled with SSL support. I wasn’t sure since I installed httperf via YUM in CentOS. I also tested by compiling myself and both versions had SSL support. If you do compile yourself you can check compile-dir/config.status and see if SSL support compiled properly.
2. Was httperf actually using SSL?
I was checking to see if this was really working by using the following command from the shell:
netstat -an | grep 443 | wc -l
This command will count how many 443 ports you have listening. So if you run a command like the following:
httperf --ssl --server 10.0.0.1 --wsesslog 1000,2,file --rate 10
Then check the server you are running the command against to see if it is actually opening new port 443 connections.