Bug 1474250 [wpt PR 11850] - Update wpt metadata, a=testonly

wpt-pr: 11850
wpt-type: metadata

testing/web-platform/meta/fetch/http-cache/cc-request.html.ini

@@ -2,3 +2,6 @@
   [HTTP cache generates 504 status code when nothing is in cache and request contains Cache-Control: only-if-cached.]
     expected: FAIL
 
+  [HTTP cache generates 504 status code when nothing is in cache and request contains Cache-Control: only-if-cached]
+    expected: FAIL
+

testing/web-platform/meta/fetch/http-cache/heuristic.html.ini

@@ -17,3 +17,21 @@
   [HTTP cache reuses a 501 Not Implemented response with Last-Modified based upon heuristic freshness.]
     expected: FAIL
 
+  [HTTP cache reuses an unknown response with Last-Modified based upon heuristic freshness when Cache-Control: public is present]
+    expected: FAIL
+
+  [HTTP cache reuses a 204 No Content response with Last-Modified based upon heuristic freshness]
+    expected: FAIL
+
+  [HTTP cache reuses a 404 Not Found response with Last-Modified based upon heuristic freshness]
+    expected: FAIL
+
+  [HTTP cache reuses a 405 Method Not Allowed response with Last-Modified based upon heuristic freshness]
+    expected: FAIL
+
+  [HTTP cache reuses a 414 URI Too Long response with Last-Modified based upon heuristic freshness]
+    expected: FAIL
+
+  [HTTP cache reuses a 501 Not Implemented response with Last-Modified based upon heuristic freshness]
+    expected: FAIL
+

testing/web-platform/meta/fetch/http-cache/partial.html.ini

@@ -29,3 +29,27 @@
   [HTTP cache stores partial response and serves smaller ranges from it(suffix-byte-range-spec).]
     expected: FAIL
 
+  [HTTP cache stores partial content and reuses it]
+    expected: FAIL
+
+  [HTTP cache stores complete response and serves smaller ranges from it (byte-range-spec)]
+    expected: FAIL
+
+  [HTTP cache stores complete response and serves smaller ranges from it (absent last-byte-pos)]
+    expected: FAIL
+
+  [HTTP cache stores complete response and serves smaller ranges from it (suffix-byte-range-spec)]
+    expected: FAIL
+
+  [HTTP cache stores partial response and serves smaller ranges from it (byte-range-spec)]
+    expected: FAIL
+
+  [HTTP cache stores partial response and serves smaller ranges from it (absent last-byte-pos)]
+    expected: FAIL
+
+  [HTTP cache stores partial response and serves smaller ranges from it (suffix-byte-range-spec)]
+    expected: FAIL
+
+  [HTTP cache stores partial content and completes it]
+    expected: FAIL
+

testing/web-platform/meta/fetch/http-cache/status.html.ini

@@ -29,3 +29,33 @@
   [HTTP cache avoids going to the network if it has a fresh 599 response.]
     expected: FAIL
 
+  [HTTP cache avoids going to the network if it has a fresh 204 response]
+    expected: FAIL
+
+  [HTTP cache avoids going to the network if it has a fresh 299 response]
+    expected: FAIL
+
+  [HTTP cache avoids going to the network if it has a fresh 400 response]
+    expected: FAIL
+
+  [HTTP cache avoids going to the network if it has a fresh 404 response]
+    expected: FAIL
+
+  [HTTP cache avoids going to the network if it has a fresh 499 response]
+    expected: FAIL
+
+  [HTTP cache avoids going to the network if it has a fresh 500 response]
+    expected: FAIL
+
+  [HTTP cache avoids going to the network if it has a fresh 502 response]
+    expected: FAIL
+
+  [HTTP cache avoids going to the network if it has a fresh 503 response]
+    expected: FAIL
+
+  [HTTP cache avoids going to the network if it has a fresh 504 response]
+    expected: FAIL
+
+  [HTTP cache avoids going to the network if it has a fresh 599 response]
+    expected: FAIL
+

testing/web-platform/meta/fetch/http-cache/vary.html.ini

@@ -2,3 +2,6 @@
   [HTTP cache doesn't invalidate existing Vary response.]
     expected: FAIL
 
+  [HTTP cache doesn't invalidate existing Vary response]
+    expected: FAIL
+