Closed Bug 1719687 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 29612 - Update split-cache.html test.

Categories

(Core :: DOM: Networking, task, P4)

Product:
Core
Component:
DOM: Networking
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
92 Branch
Tracking Flags:
Tracking Status
firefox92 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 29612 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/29612
Details from upstream follow.

b'arthursonzogni <arthursonzogni@chromium.org>' wrote:

Update split-cache.html test.

This test was requesting the same resource using fetch and using
navigations. Navigation are request with credentials. The fetch requests
weren't.

This patch updates the test to make the fetch request to send
credentials. This ensures passing this test is not simply the
consequence of discriminating anonymous and credentialled request in the
HTTP cache, but really about implementing a split cache.

This ensures implementing:
https://docs.google.com/document/d/1lvbiy4n-GM5I56Ncw304sgvY5Td32R6KHitjRXvkZ6U/edit#heading=h.i5fo7881c05m
won't cause one test case of this test to pass when split cache is
disabled.
https://chromium-review.googlesource.com/c/chromium/src/+/2964120/7/third_party/blink/web_tests/virtual/not-split-http-cache/external/wpt/fetch/http-cache/split-cache-expected.txt

Bug:1221529
Change-Id: I3e7fdfa1a21570b5128f87238238aea4a92a8a0f
Reviewed-on: https://chromium-review.googlesource.com/3015115
WPT-Export-Revision: 6bec2746299534ad8973644e0d8530e46c77b4e0

Component: web-platform-tests → DOM: Networking
Product: Testing → Core

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 41 tests and 13 subtests

Status Summary

Firefox

OK : 41
PASS : 343[Gecko-linux1804-64-qr-debug, Gecko-linux1804-64-qr-opt] 344[Gecko-android-em-7.0-x86_64-lite-qr-debug-geckoview, Gecko-android-em-7.0-x86_64-lite-qr-opt-geckoview, Gecko-linux1804-64-tsan-qr-opt, Gecko-windows10-32-qr-debug, Gecko-windows10-32-qr-opt, Gecko-windows10-64-qr-debug, Gecko-windows10-64-qr-opt, GitHub]
FAIL : 128[Gecko-android-em-7.0-x86_64-lite-qr-debug-geckoview, Gecko-android-em-7.0-x86_64-lite-qr-opt-geckoview, Gecko-linux1804-64-tsan-qr-opt, Gecko-windows10-32-qr-debug, Gecko-windows10-32-qr-opt, Gecko-windows10-64-qr-debug, Gecko-windows10-64-qr-opt, GitHub] 129[Gecko-linux1804-64-qr-debug, Gecko-linux1804-64-qr-opt]

Chrome

OK : 41
PASS : 344
FAIL : 128

Safari

OK : 31
PASS : 188
FAIL : 167
ERROR: 10

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

Firefox-only Failures

/fetch/http-cache/cache-mode.any.worker.html
Fetch sends Cache-Control: max-age=0 when cache mode is no-cache: FAIL
Fetch doesn't touch Cache-Control when cache mode is no-store and Cache-Control is already present: FAIL
Fetch doesn't touch Pragma when cache mode is no-store and Pragma is already present: FAIL
/fetch/http-cache/cache-mode.any.html
Fetch sends Cache-Control: max-age=0 when cache mode is no-cache: FAIL
Fetch doesn't touch Cache-Control when cache mode is no-store and Cache-Control is already present: FAIL
Fetch doesn't touch Pragma when cache mode is no-store and Pragma is already present: FAIL
/fetch/http-cache/cache-mode.any.serviceworker.html
Fetch sends Cache-Control: max-age=0 when cache mode is no-cache: FAIL
Fetch doesn't touch Cache-Control when cache mode is no-store and Cache-Control is already present: FAIL
Fetch doesn't touch Pragma when cache mode is no-store and Pragma is already present: FAIL

New Tests That Don't Pass

/fetch/http-cache/304-update.any.html
HTTP cache updates stored headers from a Last-Modified 304: FAIL [Gecko-linux1804-64-qr-opt], PASS [Gecko-android-em-7.0-x86_64-lite-qr-debug-geckoview, Gecko-android-em-7.0-x86_64-lite-qr-opt-geckoview, Gecko-linux1804-64-qr-debug, Gecko-linux1804-64-tsan-qr-opt, Gecko-windows10-32-qr-debug, Gecko-windows10-32-qr-opt, Gecko-windows10-64-qr-debug, Gecko-windows10-64-qr-opt, GitHub] (Chrome: PASS, Safari: FAIL)
/fetch/http-cache/304-update.any.sharedworker.html
HTTP cache updates stored headers from a Last-Modified 304: FAIL [Gecko-linux1804-64-qr-debug], PASS [Gecko-android-em-7.0-x86_64-lite-qr-debug-geckoview, Gecko-android-em-7.0-x86_64-lite-qr-opt-geckoview, Gecko-linux1804-64-qr-opt, Gecko-linux1804-64-tsan-qr-opt, Gecko-windows10-32-qr-debug, Gecko-windows10-32-qr-opt, Gecko-windows10-64-qr-debug, Gecko-windows10-64-qr-opt, GitHub] (Chrome: PASS)
/fetch/http-cache/cache-mode.any.worker.html
Fetch sends Cache-Control: max-age=0 when cache mode is no-cache: FAIL (Chrome: PASS, Safari: PASS)
Fetch doesn't touch Cache-Control when cache mode is no-store and Cache-Control is already present: FAIL (Chrome: PASS, Safari: PASS)
Fetch doesn't touch Pragma when cache mode is no-store and Pragma is already present: FAIL (Chrome: PASS, Safari: PASS)
/fetch/http-cache/cache-mode.any.sharedworker.html
Fetch sends Cache-Control: max-age=0 when cache mode is no-cache: FAIL (Chrome: PASS)
Fetch doesn't touch Cache-Control when cache mode is no-store and Cache-Control is already present: FAIL (Chrome: PASS)
Fetch doesn't touch Pragma when cache mode is no-store and Pragma is already present: FAIL (Chrome: PASS)
/fetch/http-cache/cache-mode.any.html
Fetch sends Cache-Control: max-age=0 when cache mode is no-cache: FAIL (Chrome: PASS, Safari: PASS)
Fetch doesn't touch Cache-Control when cache mode is no-store and Cache-Control is already present: FAIL (Chrome: PASS, Safari: PASS)
Fetch doesn't touch Pragma when cache mode is no-store and Pragma is already present: FAIL (Chrome: PASS, Safari: PASS)
/fetch/http-cache/cache-mode.any.serviceworker.html
Fetch sends Cache-Control: max-age=0 when cache mode is no-cache: FAIL (Chrome: PASS, Safari: PASS)
Fetch doesn't touch Cache-Control when cache mode is no-store and Cache-Control is already present: FAIL (Chrome: PASS, Safari: PASS)
Fetch doesn't touch Pragma when cache mode is no-store and Pragma is already present: FAIL (Chrome: PASS, Safari: PASS)
/fetch/http-cache/cc-request.any.worker.html
HTTP cache generates 504 status code when nothing is in cache and request contains Cache-Control: only-if-cached: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/cc-request.any.sharedworker.html
HTTP cache generates 504 status code when nothing is in cache and request contains Cache-Control: only-if-cached: FAIL (Chrome: FAIL)
/fetch/http-cache/cc-request.any.serviceworker.html
HTTP cache generates 504 status code when nothing is in cache and request contains Cache-Control: only-if-cached: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/cc-request.any.html
HTTP cache generates 504 status code when nothing is in cache and request contains Cache-Control: only-if-cached: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/heuristic.any.html
HTTP cache reuses an unknown response with Last-Modified based upon heuristic freshness when Cache-Control: public is present: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache reuses a 404 Not Found response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache reuses a 405 Method Not Allowed response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache reuses a 414 URI Too Long response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache reuses a 501 Not Implemented response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/heuristic.any.worker.html
HTTP cache reuses an unknown response with Last-Modified based upon heuristic freshness when Cache-Control: public is present: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache reuses a 404 Not Found response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache reuses a 405 Method Not Allowed response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache reuses a 414 URI Too Long response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache reuses a 501 Not Implemented response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/heuristic.any.sharedworker.html
HTTP cache reuses an unknown response with Last-Modified based upon heuristic freshness when Cache-Control: public is present: FAIL (Chrome: FAIL)
HTTP cache reuses a 404 Not Found response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL)
HTTP cache reuses a 405 Method Not Allowed response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL)
HTTP cache reuses a 414 URI Too Long response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL)
HTTP cache reuses a 501 Not Implemented response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL)
/fetch/http-cache/heuristic.any.serviceworker.html
HTTP cache reuses an unknown response with Last-Modified based upon heuristic freshness when Cache-Control: public is present: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache reuses a 404 Not Found response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache reuses a 405 Method Not Allowed response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache reuses a 414 URI Too Long response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache reuses a 501 Not Implemented response with Last-Modified based upon heuristic freshness: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/invalidate.any.worker.html
HTTP cache does not invalidate after a failed response from an unsafe request: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache does not invalidate Location URL after a failed response from an unsafe request: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache does not invalidate Content-Location URL after a failed response from an unsafe request: FAIL (Chrome: PASS, Safari: FAIL)
/fetch/http-cache/invalidate.any.sharedworker.html
HTTP cache does not invalidate after a failed response from an unsafe request: FAIL (Chrome: PASS)
HTTP cache does not invalidate Location URL after a failed response from an unsafe request: FAIL (Chrome: PASS)
HTTP cache does not invalidate Content-Location URL after a failed response from an unsafe request: FAIL (Chrome: PASS)
/fetch/http-cache/invalidate.any.serviceworker.html
HTTP cache does not invalidate after a failed response from an unsafe request: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache does not invalidate Location URL after a failed response from an unsafe request: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache does not invalidate Content-Location URL after a failed response from an unsafe request: FAIL (Chrome: PASS, Safari: FAIL)
/fetch/http-cache/invalidate.any.html
HTTP cache does not invalidate after a failed response from an unsafe request: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache does not invalidate Location URL after a failed response from an unsafe request: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache does not invalidate Content-Location URL after a failed response from an unsafe request: FAIL (Chrome: PASS, Safari: FAIL)
/fetch/http-cache/partial.any.worker.html
HTTP cache stores partial content and reuses it: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache stores complete response and serves smaller ranges from it (byte-range-spec): FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache stores complete response and serves smaller ranges from it (absent last-byte-pos): FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache stores complete response and serves smaller ranges from it (suffix-byte-range-spec): FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache stores partial response and serves smaller ranges from it (byte-range-spec): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache stores partial response and serves smaller ranges from it (absent last-byte-pos): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache stores partial response and serves smaller ranges from it (suffix-byte-range-spec): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache stores partial content and completes it: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/partial.any.html
HTTP cache stores partial content and reuses it: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache stores complete response and serves smaller ranges from it (byte-range-spec): FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache stores complete response and serves smaller ranges from it (absent last-byte-pos): FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache stores complete response and serves smaller ranges from it (suffix-byte-range-spec): FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache stores partial response and serves smaller ranges from it (byte-range-spec): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache stores partial response and serves smaller ranges from it (absent last-byte-pos): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache stores partial response and serves smaller ranges from it (suffix-byte-range-spec): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache stores partial content and completes it: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/partial.any.sharedworker.html
HTTP cache stores partial content and reuses it: FAIL (Chrome: FAIL)
HTTP cache stores complete response and serves smaller ranges from it (byte-range-spec): FAIL (Chrome: PASS)
HTTP cache stores complete response and serves smaller ranges from it (absent last-byte-pos): FAIL (Chrome: PASS)
HTTP cache stores complete response and serves smaller ranges from it (suffix-byte-range-spec): FAIL (Chrome: PASS)
HTTP cache stores partial response and serves smaller ranges from it (byte-range-spec): FAIL (Chrome: FAIL)
HTTP cache stores partial response and serves smaller ranges from it (absent last-byte-pos): FAIL (Chrome: FAIL)
HTTP cache stores partial response and serves smaller ranges from it (suffix-byte-range-spec): FAIL (Chrome: FAIL)
HTTP cache stores partial content and completes it: FAIL (Chrome: FAIL)
/fetch/http-cache/partial.any.serviceworker.html
HTTP cache stores partial content and reuses it: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache stores complete response and serves smaller ranges from it (byte-range-spec): FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache stores complete response and serves smaller ranges from it (absent last-byte-pos): FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache stores complete response and serves smaller ranges from it (suffix-byte-range-spec): FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache stores partial response and serves smaller ranges from it (byte-range-spec): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache stores partial response and serves smaller ranges from it (absent last-byte-pos): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache stores partial response and serves smaller ranges from it (suffix-byte-range-spec): FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache stores partial content and completes it: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/post-patch.any.sharedworker.html
HTTP cache uses content after PATCH request with response containing Content-Location and cache-allowing header: FAIL (Chrome: FAIL)
HTTP cache uses content after POST request with response containing Content-Location and cache-allowing header: FAIL (Chrome: FAIL)
/fetch/http-cache/post-patch.any.serviceworker.html
HTTP cache uses content after PATCH request with response containing Content-Location and cache-allowing header: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache uses content after POST request with response containing Content-Location and cache-allowing header: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/post-patch.any.html
HTTP cache uses content after PATCH request with response containing Content-Location and cache-allowing header: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache uses content after POST request with response containing Content-Location and cache-allowing header: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/post-patch.any.worker.html
HTTP cache uses content after PATCH request with response containing Content-Location and cache-allowing header: FAIL (Chrome: FAIL, Safari: FAIL)
HTTP cache uses content after POST request with response containing Content-Location and cache-allowing header: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/status.any.sharedworker.html
HTTP cache avoids going to the network if it has a fresh 299 response: FAIL (Chrome: PASS)
HTTP cache avoids going to the network if it has a fresh 400 response: FAIL (Chrome: PASS)
HTTP cache avoids going to the network if it has a fresh 404 response: FAIL (Chrome: PASS)
HTTP cache avoids going to the network if it has a fresh 499 response: FAIL (Chrome: PASS)
HTTP cache avoids going to the network if it has a fresh 500 response: FAIL (Chrome: PASS)
HTTP cache avoids going to the network if it has a fresh 502 response: FAIL (Chrome: PASS)
HTTP cache avoids going to the network if it has a fresh 503 response: FAIL (Chrome: PASS)
HTTP cache avoids going to the network if it has a fresh 504 response: FAIL (Chrome: PASS)
HTTP cache avoids going to the network if it has a fresh 599 response: FAIL (Chrome: PASS)
/fetch/http-cache/status.any.serviceworker.html
HTTP cache avoids going to the network if it has a fresh 299 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 400 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 404 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 499 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 500 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 502 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 503 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 504 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 599 response: FAIL (Chrome: PASS, Safari: FAIL)
/fetch/http-cache/status.any.worker.html
HTTP cache avoids going to the network if it has a fresh 299 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 400 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 404 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 499 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 500 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 502 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 503 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 504 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 599 response: FAIL (Chrome: PASS, Safari: FAIL)
/fetch/http-cache/status.any.html
HTTP cache avoids going to the network if it has a fresh 299 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 400 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 404 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 499 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 500 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 502 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 503 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 504 response: FAIL (Chrome: PASS, Safari: FAIL)
HTTP cache avoids going to the network if it has a fresh 599 response: FAIL (Chrome: PASS, Safari: FAIL)
/fetch/http-cache/vary.any.sharedworker.html
HTTP cache doesn't invalidate existing Vary response: FAIL (Chrome: FAIL)
/fetch/http-cache/vary.any.html
HTTP cache doesn't invalidate existing Vary response: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/vary.any.serviceworker.html
HTTP cache doesn't invalidate existing Vary response: FAIL (Chrome: FAIL, Safari: FAIL)
/fetch/http-cache/vary.any.worker.html
HTTP cache doesn't invalidate existing Vary response: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/81548cf5d411 [wpt PR 29612] - Update split-cache.html test., a=testonly

https://hg.mozilla.org/mozilla-central/rev/81548cf5d411

Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox92: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 92 Branch
You need to log in before you can comment on or make changes to this bug.