Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

date -> Last-Modified #5067

Merged
merged 1 commit into from Mar 8, 2017
Merged

date -> Last-Modified #5067

merged 1 commit into from Mar 8, 2017

Conversation

mnot
Copy link
Member

@mnot mnot commented Mar 8, 2017

to make test results a bit clearer / more consistent with what's actually happening.

@mnot
date -> Last-Modified
cd25699 
to make test results a bit clearer / more consistent with what's actually happening.
@wpt-pr-bot
Copy link
Collaborator

Notifying @annevk, @jdm, and @youennf. (Learn how reviewing works.)

@w3c-bots
Copy link

w3c-bots commented Mar 8, 2017

View the complete job log.

Firefox (nightly channel)

Testing web-platform-tests at revision 7c35da5
Using browser at version BuildID 20170306110339; SourceStamp 966464a68a2cb3ca1125808e34abb5c1d34e3797
Starting 10 test iterations
All results were stable

All results

7 tests ran
/fetch/api/request/request-cache-default-conditional.html
Subtest Results Messages
OK
RequestCache "default" mode with an If-Modified-Since header (following a request without additional headers) is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Modified-Since header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Modified-Since header (following a request without additional headers) is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Modified-Since header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Modified-Since header is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Modified-Since header is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Modified-Since header is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Modified-Since header is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-None-Match header (following a request without additional headers) is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-None-Match header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-None-Match header (following a request without additional headers) is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-None-Match header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-None-Match header is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-None-Match header is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-None-Match header is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-None-Match header is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Unmodified-Since header (following a request without additional headers) is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Unmodified-Since header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Unmodified-Since header (following a request without additional headers) is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Unmodified-Since header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Unmodified-Since header is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Unmodified-Since header is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Unmodified-Since header is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Unmodified-Since header is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Match header (following a request without additional headers) is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Match header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Match header (following a request without additional headers) is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Match header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Match header is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Match header is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Match header is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Match header is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Range header (following a request without additional headers) is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Range header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Range header (following a request without additional headers) is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Range header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Range header is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Range header is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Range header is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Range header is treated similarly to "no-store" with Last-Modified and fresh response PASS
/fetch/api/request/request-cache-default.html
Subtest Results Messages
OK
RequestCache "default" mode checks the cache for previously cached content and goes to the network for stale responses with Etag and stale response PASS
RequestCache "default" mode checks the cache for previously cached content and goes to the network for stale responses with Last-Modified and stale response PASS
RequestCache "default" mode checks the cache for previously cached content and avoids going to the network if a fresh response exists with Etag and fresh response PASS
RequestCache "default" mode checks the cache for previously cached content and avoids going to the network if a fresh response exists with Last-Modified and fresh response PASS
Responses with the "Cache-Control: no-store" header are not stored in the cache with Etag and stale response PASS
Responses with the "Cache-Control: no-store" header are not stored in the cache with Last-Modified and stale response PASS
Responses with the "Cache-Control: no-store" header are not stored in the cache with Etag and fresh response PASS
Responses with the "Cache-Control: no-store" header are not stored in the cache with Last-Modified and fresh response PASS
/fetch/api/request/request-cache-force-cache.html
Subtest Results Messages
OK
RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for stale responses with Etag and stale response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for stale responses with Last-Modified and stale response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for fresh responses with Etag and fresh response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for fresh responses with Last-Modified and fresh response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response is not found with Etag and stale response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response is not found with Last-Modified and stale response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response is not found with Etag and fresh response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response is not found with Last-Modified and fresh response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response would vary with Etag and stale response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response would vary with Last-Modified and stale response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response would vary with Etag and fresh response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response would vary with Last-Modified and fresh response PASS
RequestCache "force-cache" stores the response in the cache if it goes to the network with Etag and stale response PASS
RequestCache "force-cache" stores the response in the cache if it goes to the network with Last-Modified and stale response PASS
RequestCache "force-cache" stores the response in the cache if it goes to the network with Etag and fresh response PASS
RequestCache "force-cache" stores the response in the cache if it goes to the network with Last-Modified and fresh response PASS
/fetch/api/request/request-cache-no-cache.html
Subtest Results Messages
OK
RequestCache "no-cache" mode revalidates stale responses found in the cache with Etag and stale response PASS
RequestCache "no-cache" mode revalidates stale responses found in the cache with Last-Modified and stale response PASS
RequestCache "no-cache" mode revalidates fresh responses found in the cache with Etag and fresh response PASS
RequestCache "no-cache" mode revalidates fresh responses found in the cache with Last-Modified and fresh response PASS
/fetch/api/request/request-cache-no-store.html
Subtest Results Messages
OK
RequestCache "no-store" mode does not check the cache for previously cached content and goes to the network regardless with Etag and stale response PASS
RequestCache "no-store" mode does not check the cache for previously cached content and goes to the network regardless with Last-Modified and stale response PASS
RequestCache "no-store" mode does not check the cache for previously cached content and goes to the network regardless with Etag and fresh response PASS
RequestCache "no-store" mode does not check the cache for previously cached content and goes to the network regardless with Last-Modified and fresh response PASS
RequestCache "no-store" mode does not store the response in the cache with Etag and stale response PASS
RequestCache "no-store" mode does not store the response in the cache with Last-Modified and stale response PASS
RequestCache "no-store" mode does not store the response in the cache with Etag and fresh response PASS
RequestCache "no-store" mode does not store the response in the cache with Last-Modified and fresh response PASS
/fetch/api/request/request-cache-only-if-cached.html
Subtest Results Messages
OK
RequestCache "only-if-cached" mode checks the cache for previously cached content and avoids revalidation for stale responses with Etag and stale response PASS
RequestCache "only-if-cached" mode checks the cache for previously cached content and avoids revalidation for stale responses with Last-Modified and stale response PASS
RequestCache "only-if-cached" mode checks the cache for previously cached content and avoids revalidation for fresh responses with Etag and fresh response PASS
RequestCache "only-if-cached" mode checks the cache for previously cached content and avoids revalidation for fresh responses with Last-Modified and fresh response PASS
RequestCache "only-if-cached" mode checks the cache for previously cached content and does not go to the network if a cached response is not found with Etag and fresh response PASS
RequestCache "only-if-cached" mode checks the cache for previously cached content and does not go to the network if a cached response is not found with Last-Modified and fresh response PASS
RequestCache "only-if-cached" (with "same-origin") uses cached same-origin redirects to same-origin content with Etag and fresh response PASS
RequestCache "only-if-cached" (with "same-origin") uses cached same-origin redirects to same-origin content with Last-Modified and fresh response PASS
RequestCache "only-if-cached" (with "same-origin") uses cached same-origin redirects to same-origin content with Etag and stale response PASS
RequestCache "only-if-cached" (with "same-origin") uses cached same-origin redirects to same-origin content with Last-Modified and stale response PASS
RequestCache "only-if-cached" (with "same-origin") does not follow redirects across origins and rejects with Etag and fresh response PASS
RequestCache "only-if-cached" (with "same-origin") does not follow redirects across origins and rejects with Last-Modified and fresh response PASS
RequestCache "only-if-cached" (with "same-origin") does not follow redirects across origins and rejects with Etag and stale response PASS
RequestCache "only-if-cached" (with "same-origin") does not follow redirects across origins and rejects with Last-Modified and stale response PASS
/fetch/api/request/request-cache-reload.html
Subtest Results Messages
OK
RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Etag and stale response PASS
RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Last-Modified and stale response PASS
RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Etag and fresh response PASS
RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Last-Modified and fresh response PASS
RequestCache "reload" mode does store the response in the cache with Etag and stale response PASS
RequestCache "reload" mode does store the response in the cache with Last-Modified and stale response PASS
RequestCache "reload" mode does store the response in the cache with Etag and fresh response PASS
RequestCache "reload" mode does store the response in the cache with Last-Modified and fresh response PASS
RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Etag and stale response PASS
RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Last-Modified and stale response PASS
RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Etag and fresh response PASS
RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Last-Modified and fresh response PASS

@w3c-bots
Copy link

w3c-bots commented Mar 8, 2017

View the complete job log.

Chrome (unstable channel)

Testing web-platform-tests at revision 7c35da5
Using browser at version 58.0.3029.6 dev
Starting 10 test iterations
All results were stable

All results

7 tests ran
/fetch/api/request/request-cache-default-conditional.html
Subtest Results Messages
OK
RequestCache "default" mode with an If-Modified-Since header (following a request without additional headers) is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Modified-Since header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Modified-Since header (following a request without additional headers) is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Modified-Since header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Modified-Since header is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Modified-Since header is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Modified-Since header is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Modified-Since header is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-None-Match header (following a request without additional headers) is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-None-Match header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-None-Match header (following a request without additional headers) is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-None-Match header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-None-Match header is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-None-Match header is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-None-Match header is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-None-Match header is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Unmodified-Since header (following a request without additional headers) is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Unmodified-Since header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Unmodified-Since header (following a request without additional headers) is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Unmodified-Since header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Unmodified-Since header is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Unmodified-Since header is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Unmodified-Since header is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Unmodified-Since header is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Match header (following a request without additional headers) is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Match header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Match header (following a request without additional headers) is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Match header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Match header is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Match header is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Match header is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Match header is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Range header (following a request without additional headers) is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Range header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Range header (following a request without additional headers) is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Range header (following a request without additional headers) is treated similarly to "no-store" with Last-Modified and fresh response PASS
RequestCache "default" mode with an If-Range header is treated similarly to "no-store" with Etag and stale response PASS
RequestCache "default" mode with an If-Range header is treated similarly to "no-store" with Last-Modified and stale response PASS
RequestCache "default" mode with an If-Range header is treated similarly to "no-store" with Etag and fresh response PASS
RequestCache "default" mode with an If-Range header is treated similarly to "no-store" with Last-Modified and fresh response PASS
/fetch/api/request/request-cache-default.html
Subtest Results Messages
OK
RequestCache "default" mode checks the cache for previously cached content and goes to the network for stale responses with Etag and stale response PASS
RequestCache "default" mode checks the cache for previously cached content and goes to the network for stale responses with Last-Modified and stale response PASS
RequestCache "default" mode checks the cache for previously cached content and avoids going to the network if a fresh response exists with Etag and fresh response PASS
RequestCache "default" mode checks the cache for previously cached content and avoids going to the network if a fresh response exists with Last-Modified and fresh response PASS
Responses with the "Cache-Control: no-store" header are not stored in the cache with Etag and stale response PASS
Responses with the "Cache-Control: no-store" header are not stored in the cache with Last-Modified and stale response PASS
Responses with the "Cache-Control: no-store" header are not stored in the cache with Etag and fresh response PASS
Responses with the "Cache-Control: no-store" header are not stored in the cache with Last-Modified and fresh response PASS
/fetch/api/request/request-cache-force-cache.html
Subtest Results Messages
OK
RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for stale responses with Etag and stale response FAIL assert_equals: expected 1 but got 2
RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for stale responses with Last-Modified and stale response FAIL assert_equals: expected 1 but got 2
RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for fresh responses with Etag and fresh response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and avoid revalidation for fresh responses with Last-Modified and fresh response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response is not found with Etag and stale response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response is not found with Last-Modified and stale response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response is not found with Etag and fresh response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response is not found with Last-Modified and fresh response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response would vary with Etag and stale response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response would vary with Last-Modified and stale response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response would vary with Etag and fresh response PASS
RequestCache "force-cache" mode checks the cache for previously cached content and goes to the network if a cached response would vary with Last-Modified and fresh response PASS
RequestCache "force-cache" stores the response in the cache if it goes to the network with Etag and stale response PASS
RequestCache "force-cache" stores the response in the cache if it goes to the network with Last-Modified and stale response PASS
RequestCache "force-cache" stores the response in the cache if it goes to the network with Etag and fresh response PASS
RequestCache "force-cache" stores the response in the cache if it goes to the network with Last-Modified and fresh response PASS
/fetch/api/request/request-cache-no-cache.html
Subtest Results Messages
OK
RequestCache "no-cache" mode revalidates stale responses found in the cache with Etag and stale response PASS
RequestCache "no-cache" mode revalidates stale responses found in the cache with Last-Modified and stale response PASS
RequestCache "no-cache" mode revalidates fresh responses found in the cache with Etag and fresh response FAIL assert_equals: expected 2 but got 1
RequestCache "no-cache" mode revalidates fresh responses found in the cache with Last-Modified and fresh response FAIL assert_equals: expected 2 but got 1
/fetch/api/request/request-cache-no-store.html
Subtest Results Messages
OK
RequestCache "no-store" mode does not check the cache for previously cached content and goes to the network regardless with Etag and stale response FAIL assert_equals: expected (undefined) undefined but got (string) "\"0.18769822386767543\"";assert_equals: expected (undefined) undefined but got (string) "\"0.19314933111762667\"";assert_equals: expected (undefined) undefined but got (string) "\"0.3350900334829643\"";assert_equals: expected (undefined) undefined but got (string) "\"0.18868823617604735\"";assert_equals: expected (undefined) undefined but got (string) "\"0.3146777808977581\"";assert_equals: expected (undefined) undefined but got (string) "\"0.34217097749758696\"";assert_equals: expected (undefined) undefined but got (string) "\"0.10690916529590866\"";assert_equals: expected (undefined) undefined but got (string) "\"0.7084931748818781\"";assert_equals: expected (undefined) undefined but got (string) "\"0.2645453008012395\"";assert_equals: expected (undefined) undefined but got (string) "\"0.2719826867576247\""
RequestCache "no-store" mode does not check the cache for previously cached content and goes to the network regardless with Last-Modified and stale response FAIL assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:41 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:13 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:21:29 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:27 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:42 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:21:58 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:57 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:27 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:12 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:21:43 GMT"
RequestCache "no-store" mode does not check the cache for previously cached content and goes to the network regardless with Etag and fresh response FAIL assert_equals: expected 2 but got 1
RequestCache "no-store" mode does not check the cache for previously cached content and goes to the network regardless with Last-Modified and fresh response FAIL assert_equals: expected 2 but got 1
RequestCache "no-store" mode does not store the response in the cache with Etag and stale response FAIL assert_equals: expected (undefined) undefined but got (string) "\"0.7644127807589494\"";assert_equals: expected (undefined) undefined but got (string) "\"0.9401330736357034\"";assert_equals: expected (undefined) undefined but got (string) "\"0.40322232049602547\"";assert_equals: expected (undefined) undefined but got (string) "\"0.26000032651498706\"";assert_equals: expected (undefined) undefined but got (string) "\"0.9310239121829862\"";assert_equals: expected (undefined) undefined but got (string) "\"0.6793800251652118\"";assert_equals: expected (undefined) undefined but got (string) "\"0.7571626528973601\"";assert_equals: expected (undefined) undefined but got (string) "\"0.6358076128744294\"";assert_equals: expected (undefined) undefined but got (string) "\"0.7191021154365187\"";assert_equals: expected (undefined) undefined but got (string) "\"0.5865450620059982\""
RequestCache "no-store" mode does not store the response in the cache with Last-Modified and stale response FAIL assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:41 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:13 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:21:29 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:27 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:42 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:21:58 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:57 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:27 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:12 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:21:43 GMT"
RequestCache "no-store" mode does not store the response in the cache with Etag and fresh response FAIL assert_equals: expected 2 but got 1
RequestCache "no-store" mode does not store the response in the cache with Last-Modified and fresh response FAIL assert_equals: expected 2 but got 1
/fetch/api/request/request-cache-only-if-cached.html
Subtest Results Messages
OK
RequestCache "only-if-cached" mode checks the cache for previously cached content and avoids revalidation for stale responses with Etag and stale response FAIL assert_equals: expected 1 but got 2
RequestCache "only-if-cached" mode checks the cache for previously cached content and avoids revalidation for stale responses with Last-Modified and stale response FAIL assert_equals: expected 1 but got 2
RequestCache "only-if-cached" mode checks the cache for previously cached content and avoids revalidation for fresh responses with Etag and fresh response PASS
RequestCache "only-if-cached" mode checks the cache for previously cached content and avoids revalidation for fresh responses with Last-Modified and fresh response PASS
RequestCache "only-if-cached" mode checks the cache for previously cached content and does not go to the network if a cached response is not found with Etag and fresh response FAIL assert_true: fetch should have been an error expected true got false
RequestCache "only-if-cached" mode checks the cache for previously cached content and does not go to the network if a cached response is not found with Last-Modified and fresh response FAIL assert_true: fetch should have been an error expected true got false
RequestCache "only-if-cached" (with "same-origin") uses cached same-origin redirects to same-origin content with Etag and fresh response PASS
RequestCache "only-if-cached" (with "same-origin") uses cached same-origin redirects to same-origin content with Last-Modified and fresh response PASS
RequestCache "only-if-cached" (with "same-origin") uses cached same-origin redirects to same-origin content with Etag and stale response FAIL assert_equals: expected 2 but got 4
RequestCache "only-if-cached" (with "same-origin") uses cached same-origin redirects to same-origin content with Last-Modified and stale response FAIL assert_equals: expected 2 but got 4
RequestCache "only-if-cached" (with "same-origin") does not follow redirects across origins and rejects with Etag and fresh response PASS
RequestCache "only-if-cached" (with "same-origin") does not follow redirects across origins and rejects with Last-Modified and fresh response PASS
RequestCache "only-if-cached" (with "same-origin") does not follow redirects across origins and rejects with Etag and stale response FAIL assert_equals: expected 2 but got 3
RequestCache "only-if-cached" (with "same-origin") does not follow redirects across origins and rejects with Last-Modified and stale response FAIL assert_equals: expected 2 but got 3
/fetch/api/request/request-cache-reload.html
Subtest Results Messages
OK
RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Etag and stale response FAIL assert_equals: expected (undefined) undefined but got (string) "\"0.725625648132094\"";assert_equals: expected (undefined) undefined but got (string) "\"0.5995108278832195\"";assert_equals: expected (undefined) undefined but got (string) "\"0.7265547229121594\"";assert_equals: expected (undefined) undefined but got (string) "\"0.34046368960033124\"";assert_equals: expected (undefined) undefined but got (string) "\"0.32992378866001904\"";assert_equals: expected (undefined) undefined but got (string) "\"0.9248608464715438\"";assert_equals: expected (undefined) undefined but got (string) "\"0.17923820044323913\"";assert_equals: expected (undefined) undefined but got (string) "\"0.9239347548420107\"";assert_equals: expected (undefined) undefined but got (string) "\"0.8148780776786144\"";assert_equals: expected (undefined) undefined but got (string) "\"0.43579027962017003\""
RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Last-Modified and stale response FAIL assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:30 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:44 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:15 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:21:45 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:15 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:00 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:29 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:21:31 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:45 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:01 GMT"
RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Etag and fresh response FAIL assert_equals: expected 2 but got 1
RequestCache "reload" mode does not check the cache for previously cached content and goes to the network regardless with Last-Modified and fresh response FAIL assert_equals: expected 2 but got 1
RequestCache "reload" mode does store the response in the cache with Etag and stale response PASS
RequestCache "reload" mode does store the response in the cache with Last-Modified and stale response PASS
RequestCache "reload" mode does store the response in the cache with Etag and fresh response PASS
RequestCache "reload" mode does store the response in the cache with Last-Modified and fresh response PASS
RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Etag and stale response FAIL assert_equals: expected (undefined) undefined but got (string) "\"0.6704770979646109\"";assert_equals: expected (undefined) undefined but got (string) "\"0.26476398469537976\"";assert_equals: expected (undefined) undefined but got (string) "\"0.070567291658574\"";assert_equals: expected (undefined) undefined but got (string) "\"0.46860790654480855\"";assert_equals: expected (undefined) undefined but got (string) "\"0.5999470654582479\"";assert_equals: expected (undefined) undefined but got (string) "\"0.9070041864934928\"";assert_equals: expected (undefined) undefined but got (string) "\"0.8864854689955146\"";assert_equals: expected (undefined) undefined but got (string) "\"0.6045316478596721\"";assert_equals: expected (undefined) undefined but got (string) "\"0.25316444980313557\"";assert_equals: expected (undefined) undefined but got (string) "\"0.21726962124927685\""
RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Last-Modified and stale response FAIL assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:30 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:44 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:15 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:21:45 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:15 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:00 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:23:29 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:21:31 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:45 GMT";assert_equals: expected (undefined) undefined but got (string) "Wed, 08 Mar 2017 03:22:01 GMT"
RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Etag and fresh response FAIL assert_equals: expected 2 but got 1
RequestCache "reload" mode does store the response in the cache even if a previous response is already stored with Last-Modified and fresh response FAIL assert_equals: expected 2 but got 1

@annevk annevk merged commit 7b351e5 into web-platform-tests:master Mar 8, 2017
@mnot mnot deleted the patch-1 branch March 9, 2017 01:44
@mnot mnot restored the patch-1 branch March 9, 2017 01:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
fetch
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@mnot @wpt-pr-bot @w3c-bots @annevk