add preliminary SSL support

This will also be the foundation of SSL support in Rainbows!
and Zbatery.  Some users may also want to use this in
Unicorn on LANs to meet certain security/auditing requirements.
Of course, Nightmare! (in whatever form) should also be able to
use it.

1 files changed, 48 insertions, 0 deletions

diff --git a/t/t0600-https-server-basic.sh b/t/t0600-https-server-basic.sh
new file mode 100755
index 0000000..5dd0d65
--- /dev/null
+++ b/t/t0600-https-server-basic.sh
@@ -0,0 +1,48 @@
+#!/bin/sh
+. ./test-lib.sh
+t_plan 7 "simple HTTPS connection tests"
+
+t_begin "setup and start" && {
+        rtmpfiles curl_err
+        unicorn_setup
+cat > $unicorn_config <<EOF
+ssl do
+  listen "$listen"
+  ssl_certificate "server.crt"
+  ssl_certificate_key "server.key"
+end
+pid "$pid"
+stderr_path "$r_err"
+stdout_path "$r_out"
+EOF
+        unicorn -D -c $unicorn_config env.ru
+        unicorn_wait_start
+}
+
+t_begin "single request" && {
+        curl -sSfv --cacert ca.crt https://$listen/
+}
+
+t_begin "check stderr has no errors" && {
+        check_stderr
+}
+
+t_begin "multiple requests" && {
+        curl -sSfv --no-keepalive --cacert ca.crt \
+                https://$listen/ https://$listen/ 2>> $curl_err >> $tmp
+                dbgcat curl_err
+}
+
+t_begin "check stderr has no errors" && {
+        check_stderr
+}
+
+t_begin "killing succeeds" && {
+        kill $unicorn_pid
+}
+
+t_begin "check stderr has no errors" && {
+        check_stderr
+}
+
+t_done