The framework bugs which used to affect this test case have long since

been fixed, so remove the workarounds.  Also stop testing things which
are not intended to work.

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

diff --git a/varnish-tools/regress/lib/Varnish/Test/Case/POST.pm b/varnish-tools/regress/lib/Varnish/Test/Case/POST.pm
index aa13a1402626ca45df498705c8c63ea5e809a262..76eb9f1ba10414debda036921fc3b29d311752fd 100644 (file)
--- a/varnish-tools/regress/lib/Varnish/Test/Case/POST.pm
+++ b/varnish-tools/regress/lib/Varnish/Test/Case/POST.pm
@@ -36,15 +36,6 @@ use base 'Varnish::Test::Case';
 our $DESCR = "Tests Varnish's ability to correctly pass POST requests" .
     " to the backend, and their replies back to the client.";
 
-# testCachePOST and testPassPOST are known to fail, and it is not
-# clear at this point whether that is a bug or a feature.
-#
-# More interestingly, if you run testPassPOST before testPipePOST, the
-# latter receives the Varnish Guru Meditation intended for the former.
-# This seems to be a bug in either IO::Multiplex or Varnish::Test.
-#
-our @TESTS = qw(testPipePOST testCachePOST testPassPOST);
-
 our $VCL = <<EOVCL;
 sub vcl_recv {
     if (req.request == "POST") {
@@ -113,6 +104,10 @@ sub testCachePOST($) {
 sub server_get($$$) {
     my ($self, $request, $response) = @_;
 
+    # Varnish will always use GET when fetching a presumably cacheable
+    # object from the backend.  This is not a bug.
+    goto &server_post
+       if ($request->uri =~ m/cache_me/);
     die "Got GET request instead of POST\n";
 }