about summary refs log tree commit homepage
path: root/t/t0200-rack-hijack.sh
diff options
context:
space:
mode:
authorEric Wong <e@80x24.org>2015-06-09 20:17:18 +0000
committerEric Wong <e@80x24.org>2015-06-10 09:18:59 +0000
commit02a072734906ac4c1ea77990207b84895ab4a7cb (patch)
tree04abb7b53211c779637ab5a2f0e2930dbbd2ac6d /t/t0200-rack-hijack.sh
parent40b9812029848933037466b2e7b19a47cfbd8363 (diff)
downloadunicorn-02a072734906ac4c1ea77990207b84895ab4a7cb.tar.gz
Middlewares such as Rack::Lock (used by Rails) break badly unless
the response body is closed on hijack, so we will close it to follow
the lead of other popular Rack servers.

While it's unclear if there's anybody using rack.hijack with unicorn,
we'll try to emulate the behavior of other servers as much as
possible.

ref: https://github.com/ngauthier/tubesock/issues/10
Diffstat (limited to 't/t0200-rack-hijack.sh')
-rwxr-xr-xt/t0200-rack-hijack.sh7
1 files changed, 5 insertions, 2 deletions
diff --git a/t/t0200-rack-hijack.sh b/t/t0200-rack-hijack.sh
index f772071..de3eb82 100755
--- a/t/t0200-rack-hijack.sh
+++ b/t/t0200-rack-hijack.sh
@@ -16,12 +16,15 @@ t_begin "check response hijack" && {
         test "xresponse.hijacked" = x"$(curl -sSfv http://$listen/hijack_res)"
 }
 
-t_begin "killing succeeds" && {
+t_begin "killing succeeds after hijack" && {
         kill $unicorn_pid
 }
 
-t_begin "check stderr" && {
+t_begin "check stderr for hijacked body close" && {
         check_stderr
+        grep 'closed DieIfUsed 1\>' $r_err
+        grep 'closed DieIfUsed 2\>' $r_err
+        ! grep 'closed DieIfUsed 3\>' $r_err
 }
 
 t_done