如何使用ApacheBench修复"ssl握手失败"？

Question

当我使用ApacheBench测试https时,会返回错误,"ssl handshake failed".

如何使用ApacheBench测试https？

Answer 1

ApacheBench似乎无法忽略证书问题(至少其中一些),所以我编写了这个脚本:

#!/bin/bash
K=200;    
HTTPSA='https://192.168.1.103:443/'    
date +%M-%S-%N>wgetres.txt
for (( c=1; c<=$K; c++ ))
do
    wget --no-check-certificate --secure-protocol=SSLv3 --spider $HTTPSA
done
date +%M-%S-%N>>wgetres.txt

它没有AB那么精确,但却给出了这个想法.在比较测试中做得好.

Answer 2

httperf也是单线程的,但截至今天(2012年8月31日),它正确处理SSL,甚至还有一些围绕SSL的有用的附加功能:

  --ssl  Specifies that all communication between httperf and the server
      should  utilize  the  Secure Sockets Layer (SSL) protocol.  This
      option is available only if httperf was compiled with  SSL  supâ€
      port enabled.

  --ssl-ciphers=L
      This  option  is  only  meaningful  if  SSL is in use (see --ssl
      option).  This option specifies the list L of cipher suites that
      httperf  may  use  in  negotiating  a secure connection with the
      server.  If the list contains more than one  cipher  suite,  the
      ciphers  must  be  separated by a colon.  If the server does not
      accept any of the listed cipher suites,  the  connection  estabâ€
      lishment  will  fail and httperf will exit immediately.  If this
      option is not specified when the --ssl option  is  present  then
      httperf  will use all of the SSLv3 cipher suites provided by the
      underlying SSL library.

 --ssl-no-reuse
      This option is only meaningful if SSL and sessions  are  in  use
      (see  --ssl,  --wsess,  --wsesslog).   When an SSL connection is
      established the client receives a  session  identifier  (session
      id)  from the server.  On subsequent SSL connections, the client
      normally reuses this session id in order to avoid the expense of
      repeating  the  (slow) SSL handshake to establish a new SSL sesâ€
      sion and obtain another session id (even if the client  attempts
      to re-use a session id, the server may force the client to reneâ€
      gotiate a session).  By default httperf reuses  the  session  id
      across  all  connections  in  a  session.  If the --ssl-no-reuse
      option is in effect, then httperf will not reuse the session id,
      and the entire SSL handshake will be performed for each new conâ€
      nection in a session.