Update web-platform-tests to revision 58eb04cecbbec2e18531ab440225e38944a9c444

tests/wpt/metadata/fetch/http-cache/304-update.html.ini

@@ -0,0 +1,14 @@
+[304-update.html]
+  type: testharness
+  [HTTP cache updates returned headers from a Last-Modified 304.]
+    expected: FAIL
+
+  [HTTP cache updates stored headers from a Last-Modified 304.]
+    expected: FAIL
+
+  [HTTP cache updates returned headers from a ETag 304.]
+    expected: FAIL
+
+  [HTTP cache updates stored headers from a ETag 304.]
+    expected: FAIL
+

tests/wpt/metadata/fetch/http-cache/cc-request.html.ini

@@ -0,0 +1,11 @@
+[cc-request.html]
+  type: testharness
+  [HTTP cache does use aged stale response when request contains Cache-Control: max-stale that permits its use.]
+    expected: FAIL
+
+  [HTTP cache does reuse stale response with Age header when request contains Cache-Control: max-stale that permits its use.]
+    expected: FAIL
+
+  [HTTP cache generates 504 status code when nothing is in cache and request contains Cache-Control: only-if-cached.]
+    expected: FAIL
+

tests/wpt/metadata/fetch/http-cache/freshness.html.ini

@@ -0,0 +1,20 @@
+[freshness.html]
+  type: testharness
+  [HTTP cache reuses a response with a future Expires.]
+    expected: FAIL
+
+  [HTTP cache reuses a response with positive Cache-Control: max-age.]
+    expected: FAIL
+
+  [HTTP cache reuses a response with positive Cache-Control: max-age and a past Expires.]
+    expected: FAIL
+
+  [HTTP cache reuses a response with positive Cache-Control: max-age and an invalid Expires.]
+    expected: FAIL
+
+  [HTTP cache stores a response with Cache-Control: no-cache, but revalidates upon use.]
+    expected: FAIL
+
+  [HTTP cache stores a response with Cache-Control: no-cache, but revalidates upon use, even with max-age and Expires.]
+    expected: FAIL
+

tests/wpt/metadata/fetch/http-cache/heuristic.html.ini

@@ -0,0 +1,29 @@
+[heuristic.html]
+  type: testharness
+  [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 200 OK response with Last-Modified based upon heuristic freshness.]
+    expected: FAIL
+
+  [HTTP cache reuses a 203 Non-Authoritative Information response with Last-Modified based upon heuristic freshness.]
+    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 410 Gone 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
+

tests/wpt/metadata/fetch/http-cache/invalidate.html.ini

@@ -0,0 +1,20 @@
+[invalidate.html]
+  type: testharness
+  [HTTP cache does not invalidate after a failed response from an unsafe request]
+    expected: FAIL
+
+  [HTTP cache invalidates after a successful response from an unknown method]
+    expected: FAIL
+
+  [HTTP cache does not invalidate Location URL after a failed response from an unsafe request]
+    expected: FAIL
+
+  [HTTP cache invalidates Location URL after a successful response from an unknown method]
+    expected: FAIL
+
+  [HTTP cache does not invalidate Content-Location URL after a failed response from an unsafe request]
+    expected: FAIL
+
+  [HTTP cache invalidates Content-Location URL after a successful response from an unknown method]
+    expected: FAIL
+

tests/wpt/metadata/fetch/http-cache/partial.html.ini

@@ -0,0 +1,14 @@
+[partial.html]
+  type: testharness
+  [HTTP cache stores partial content and reuses it.]
+    expected: FAIL
+
+  [HTTP cache stores complete response and serves smaller ranges from it.]
+    expected: FAIL
+
+  [HTTP cache stores partial response and serves smaller ranges from it.]
+    expected: FAIL
+
+  [HTTP cache stores partial content and completes it.]
+    expected: FAIL
+

tests/wpt/metadata/fetch/http-cache/status.html.ini

@@ -0,0 +1,41 @@
+[status.html]
+  type: testharness
+  [HTTP cache avoids going to the network if it has a fresh 200 response.]
+    expected: FAIL
+
+  [HTTP cache avoids going to the network if it has a fresh 203 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 410 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
+

tests/wpt/metadata/fetch/http-cache/vary.html.ini

@@ -0,0 +1,17 @@
+[vary.html]
+  type: testharness
+  [HTTP cache reuses Vary response when request matches.]
+    expected: FAIL
+
+  [HTTP cache doesn't invalidate existing Vary response.]
+    expected: FAIL
+
+  [HTTP cache doesn't pay attention to headers not listed in Vary.]
+    expected: FAIL
+
+  [HTTP cache reuses two-way Vary response when request matches.]
+    expected: FAIL
+
+  [HTTP cache reuses three-way Vary response when request matches.]
+    expected: FAIL
+