[master] 51a54fbd3 Backend send_timeout coverage
Dridi Boukelmoune
dridi.boukelmoune at gmail.com
Mon Apr 29 15:30:12 UTC 2019
commit 51a54fbd344bb2fb2ca08c945b0331873b8cd799
Author: Dridi Boukelmoune <dridi.boukelmoune at gmail.com>
Date: Mon Apr 29 17:22:21 2019 +0200
Backend send_timeout coverage
Despite v1l code being used for both client responses and backend
requests, the send timeouts only kicks in on the client side. The
backend code does not enter the send loop subject to the timeout
for lack of niov at V1L_Open() time.
Refs 43bbe97b38a86d706c0d9f4838bbfbd305342775
diff --git a/bin/varnishtest/tests/s00011.vtc b/bin/varnishtest/tests/s00011.vtc
new file mode 100644
index 000000000..50e6e4612
--- /dev/null
+++ b/bin/varnishtest/tests/s00011.vtc
@@ -0,0 +1,25 @@
+varnishtest "backend send timeouts"
+
+server s1 {
+ rxreq
+ expect req.method == POST
+ expect req.body == helloworld
+ txresp
+} -start
+
+varnish v1 -vcl+backend "" -start
+
+# Despite shared code, these parameters are only for client responses.
+# See 43bbe97b38a86d706c0d9f4838bbfbd305342775.
+
+varnish v1 -cliok "param.set idle_send_timeout 1"
+varnish v1 -cliok "param.set send_timeout 1"
+
+client c1 {
+ txreq -method POST -hdr "Content-Length: 10"
+ send hello
+ delay 2
+ send world
+ rxresp
+ expect resp.status == 200
+} -run
More information about the varnish-commit
mailing list