Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(201)

Side by Side Diff: third_party/WebKit/LayoutTests/external/wpt/fetch/http-cache/cc-request-expected.txt

Issue 2778753002: Import //fetch from Web Platform Tests. (Closed)
Patch Set: Baselines. Created 3 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
(Empty)
1 This is a testharness.js-based test.
2 PASS HTTP cache doesn't use aged but fresh response when request contains Cache- Control: max-age=0.
3 FAIL HTTP cache doesn't use aged but fresh response when request contains Cache- Control: max-age=1. assert_equals: Response used expected 2 but got 1
4 FAIL HTTP cache doesn't use fresh response with Age header when request contains Cache-Control: max-age that is greater than remaining freshness. assert_equals: Response used expected 2 but got 1
5 FAIL HTTP cache does use aged stale response when request contains Cache-Control : max-stale that permits its use. assert_less_than: Response used expected a num ber less than 2 but got 2
6 FAIL HTTP cache does reuse stale response with Age header when request contains Cache-Control: max-stale that permits its use. assert_less_than: Response used e xpected a number less than 2 but got 2
7 FAIL HTTP cache doesn't reuse fresh response when request contains Cache-Control : min-fresh that wants it fresher. assert_equals: Response used expected 2 but g ot 1
8 FAIL HTTP cache doesn't reuse fresh response with Age header when request contai ns Cache-Control: min-fresh that wants it fresher. assert_equals: Response used expected 2 but got 1
9 PASS HTTP cache doesn't reuse fresh response when request contains Cache-Control : no-cache.
10 PASS HTTP cache validates fresh response with Last-Modified when request contain s Cache-Control: no-cache.
11 PASS HTTP cache validates fresh response with ETag when request contains Cache-C ontrol: no-cache.
12 FAIL HTTP cache doesn't reuse fresh response when request contains Cache-Control : no-store. assert_equals: Response used expected 2 but got 1
13 FAIL HTTP cache generates 504 status code when nothing is in cache and request c ontains Cache-Control: only-if-cached. assert_equals: Response status expected 5 04 but got 200
14 Harness: the test ran to completion.
15
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698