title: Why is the "Siege"-tool not working with HTTPS sites?
body: <p>I am using Siege 3.0.3 from CentOS 6.4.</p>
  
  <p>My question is : how does 'Siege' supports HTTPS protocol?</p>
  
  <p>So far using this tool the HTTP sites testing is OK.</p>
  
  <p>But, I am facing certain issues (all described below) while dealing with the HTTPS sites.</p>
  
  <p>As suggested by someone, to make HTTPS work I have compiled siege with openssl.</p>
  
  <p>For doing this, I followed the procedure as mentioned in the below site.
  <a href="http://drewsymo.com/how-to/installing-siege-stress-tester-on-centos-6-3/" rel="nofollow">http://drewsymo.com/how-to/installing-siege-stress-tester-on-centos-6-3/</a></p>
  
  <p>In brief, I ran the following commands for compiling siege with openssl.</p>
  
  <pre><code>cd /opt
  wget http://www.openssl.org/source/openssl-1.0.1e.tar.gz
  tar -zxvf openssl-1.0.1e.tar.gz
  cd siege-3.0.3
  ./configure -with-ssl=/opt/openssl-1.0.1e
  make &amp;&amp; make install
  </code></pre>
  
  <p>I did not got any warning or errors in the above steps.</p>
  
  <p>But, even after this I am getting the below results while dealing with HTTPs sites using this tool.</p>
  
  <p>ISSUE#1</p>
  
  <p>Whenever I set many hits like 1000, 2000 I get the below error.</p>
  
  <pre><code>"Segmentation fault (core dumped)"
  </code></pre>
  
  <p>Kindly note I have already ran the "ulimit -n 10000" command to increase the number of open files.</p>
  
  <p>But, this did not helped.</p>
  
  <p>ISSUE#2</p>
  
  <pre><code>[root@localhost ~]# siege --user-agent="Mozilla/5.0 (Windows NT 6.2; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0" -c10 -r1 -t50S someHTTPSdomain.com
  [error] CONFIG conflict: selected time and repetition based testing: No such file or directory
  defaulting to time-based testing: 50 seconds
  ** SIEGE 3.0.3
  ** Preparing 10 concurrent users for battle.
  The server is now under siege...
  HTTP/1.1 302   0.09 secs:       0 bytes ==&gt; GET  /
  HTTP/1.1 302   0.11 secs:       0 bytes ==&gt; GET  /
  HTTP/1.1 302   0.08 secs:       0 bytes ==&gt; GET  /
  HTTP/1.1 302   3.09 secs:       0 bytes ==&gt; GET  /
  .....................
  .....................
  .....................
  
  Then after many such hits exceeding the above defined 10 hits, I had to press Ctrl+C.
  
  After that, it shows,
  
  ^C
  Lifting the server siege...      done.
  
  Transactions:                      0 hits
  Availability:                   0.00 %
  Elapsed time:                  18.70 secs
  Data transferred:               0.00 MB
  Response time:                  0.00 secs
  Transaction rate:               0.00 trans/sec
  Throughput:                     0.00 MB/sec
  Concurrency:                    3.19
  Successful transactions:          30
  Failed transactions:              28
  Longest transaction:           12.10
  Shortest transaction:           0.07
  
  FILE: /usr/local/var/siege.log
  You can disable this annoying message by editing
  the .siegerc file in your home directory; change
  the directive 'show-logfile' to false.
  [root@localhost ~]#
  </code></pre>
  
  <p>Why the transactions showing 0 hits always in case of HTTPS sites?</p>
  
  <p>Even after specifying "-c10 -r1" why the scrolling output not stopping for HTTPS sites?</p>
  
  <p>Also, why all the HTTP responses are showing 30X for HTTPS sites?</p>
  
  <p>Why this error "[error] CONFIG conflict: selected time and repetition based testing: No such file or directory defaulting to time-based testing: 50 seconds" keep showing?</p>
  
  <p>Anyway, if I remove the -t50S from the above command I do not get the error "[error] CONFIG conflict: selected time and repetition based testing: No such file or directory defaulting to time-based testing: 50 seconds".</p>
  
  <p>But, still it shows the transactions as 0 hits. See below.</p>
  
  <pre><code>[root@localhost ~]# siege --user-agent="Mozilla/5.0 (Windows NT 6.2; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0" -c10 -r1 someHTTPSdomain.com
  ** SIEGE 3.0.3
  ** Preparing 10 concurrent users for battle.
  The server is now under siege...
  HTTP/1.1 302   0.08 secs:       0 bytes ==&gt; GET  /
  HTTP/1.1 302   0.08 secs:       0 bytes ==&gt; GET  /
  HTTP/1.1 302   0.09 secs:       0 bytes ==&gt; GET  /
  HTTP/1.1 302   0.11 secs:       0 bytes ==&gt; GET  /
  HTTP/1.1 302   0.07 secs:       0 bytes ==&gt; GET  /
  HTTP/1.1 302   0.09 secs:       0 bytes ==&gt; GET  /
  HTTP/1.1 302   0.08 secs:       0 bytes ==&gt; GET  /
  HTTP/1.1 302   0.08 secs:       0 bytes ==&gt; GET  /
  HTTP/1.1 302   0.08 secs:       0 bytes ==&gt; GET  /
  HTTP/1.1 302   0.10 secs:       0 bytes ==&gt; GET  /
  done.
  
  Transactions:                      0 hits
  Availability:                   0.00 %
  Elapsed time:                   2.14 secs
  Data transferred:               0.00 MB
  Response time:                  0.00 secs
  Transaction rate:               0.00 trans/sec
  Throughput:                     0.00 MB/sec
  Concurrency:                    0.40
  Successful transactions:          10
  Failed transactions:              10
  Longest transaction:            0.11
  Shortest transaction:           0.07
  
  FILE: /usr/local/var/siege.log
  You can disable this annoying message by editing
  the .siegerc file in your home directory; change
  the directive 'show-logfile' to false.
  [root@localhost ~]#
  </code></pre>
  
  <p>ISSUE#3</p>
  
  <p>Another thing, I noticed if I prefix the HTTPS URL with a "https://" like the below, I get output like this.</p>
  
  <pre><code>[root@localhost ~]# siege --user-agent="Mozilla/5.0 (Windows NT 6.2; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0" -c10 -r1 https://someHTTPSdomain.com
  ** SIEGE 3.0.3
  ** Preparing 10 concurrent users for battle.
  The server is now under siege...
  done.
  
  Transactions:                      0 hits
  Availability:                   0.00 %
  Elapsed time:                   1.06 secs
  Data transferred:               0.00 MB
  Response time:                  0.00 secs
  Transaction rate:               0.00 trans/sec
  Throughput:                     0.00 MB/sec
  Concurrency:                    0.00
  Successful transactions:           0
  Failed transactions:              10
  Longest transaction:            0.00
  Shortest transaction:           0.00
  
  FILE: /usr/local/var/siege.log
  You can disable this annoying message by editing
  the .siegerc file in your home directory; change
  the directive 'show-logfile' to false.
  [root@localhost ~]#
  </code></pre>
  
  <p>Simply, no HTTP or other response messages.</p>
  
  <p>I am confused with these results while dealing with the HTTPS sites. Not clear whether I did anything wrong while issuing the commands or it's some bug or limitation of this tool.</p>
  
  <p>I like to mention that in my above commands I have used a valid Windows 8 (using a Firefox browser) useragent by using "<strong>--user-agent=</strong>" in all the commands.
  I did like this only to replace the default Siege useragent which is "<strong>JoeDog/1.00 [en] (X11; I; Siege 3.0.3)</strong>" as this default Siege useragent might be blacklisted in many webservers (not so sure).</p>
  
  <p>Kindly someone guide.</p>
  
  <p>Thanks in advance.</p>