Responses in one of the Ingress type tests are uncacheable.

Cached responses were interfering with other tests when the e2e test
script was run.

test/e2e/ingresses/fanout-nohost.vtc

@@ -3,31 +3,33 @@
 varnishtest "simple fanout by path with no host specified in Ingress"
 
 client c1 -connect "${localhost} ${localport}" {
-	txreq -url /coffee/foo/bar -hdr "Host: example.com"
+	txreq -url /coffee/foo/bar -hdr "Host: example.com" \
+            -hdr "X-Set-Cache-Control: public, max-age=0"
 	rxresp
 	expect resp.status == 200
 	expect resp.body ~ "(?m)^URI: /coffee/foo/bar$"
 	expect resp.body ~ "(?m)^Server name: coffee-[a-z0-9]+-[a-z0-9]+$"
 
-	txreq -url /tea/baz/quux -hdr "Host: example.org"
+	txreq -url /tea/baz/quux -hdr "Host: example.org" \
+            -hdr "X-Set-Cache-Control: public, max-age=0"
 	rxresp
 	expect resp.status == 200
 	expect resp.body ~ "(?m)^URI: /tea/baz/quux$"
 	expect resp.body ~ "(?m)^Server name: tea-[a-z0-9]+-[a-z0-9]+$"
 
-	txreq -url /coffee/foo/bar
+	txreq -url /coffee/foo/bar -hdr "X-Set-Cache-Control: public, max-age=0"
 	rxresp
 	expect resp.status == 200
 	expect resp.body ~ "(?m)^URI: /coffee/foo/bar$"
 	expect resp.body ~ "(?m)^Server name: coffee-[a-z0-9]+-[a-z0-9]+$"
 
-	txreq -url /tea/baz/quux
+	txreq -url /tea/baz/quux  -hdr "X-Set-Cache-Control: public, max-age=0"
 	rxresp
 	expect resp.status == 200
 	expect resp.body ~ "(?m)^URI: /tea/baz/quux$"
 	expect resp.body ~ "(?m)^Server name: tea-[a-z0-9]+-[a-z0-9]+$"
 
-	txreq -url /milk
+	txreq -url /milk -hdr "X-Set-Cache-Control: public, max-age=0"
 	rxresp
 	expect resp.status == 404
 } -run