Add a test case for the root cause of #164, which is that the backend sends

a garbled response (or no response at all).

git-svn-id: svn+ssh://projects.linpro.no/svn/varnish/trunk@2160 d4fa192b-c00b-0410-8231-f00ffab90ce4

diff --git a/varnish-tools/regress/lib/Varnish/Test/Server/Connection.pm b/varnish-tools/regress/lib/Varnish/Test/Server/Connection.pm
index 70893189a841a8ec417d6e3e208125b8dd7e55a0..6758e8a1da9d2ec2e0d71bfcf485913b1683783d 100644 (file)
--- a/varnish-tools/regress/lib/Varnish/Test/Server/Connection.pm
+++ b/varnish-tools/regress/lib/Varnish/Test/Server/Connection.pm
@@ -67,6 +67,20 @@ sub new($$) {
     return $self;
 }
 
+=head2 write
+
+Write data to the connection
+
+=cut
+
+sub write($@) {
+    my ($self, @data) = @_;
+
+    foreach my $data (@data) {
+       $self->{'mux'}->write($self->{'fh'}, $data);
+    }
+}
+
 =head2 send_response
 
 Called by test-cases to send a given HTTP::Response object out on the