Make registration.update() no longer force bypassing the HTTP cache (1/2)

LayoutTests/http/tests/serviceworker/ServiceWorkerGlobalScope/resources/update-worker.php

Index: LayoutTests/http/tests/serviceworker/ServiceWorkerGlobalScope/resources/update-worker.php
diff --git a/LayoutTests/http/tests/serviceworker/ServiceWorkerGlobalScope/resources/update-worker.php b/LayoutTests/http/tests/serviceworker/ServiceWorkerGlobalScope/resources/update-worker.php
index 2486820c26c5f6483270a2d15f6527ec3ee11662..7557e41d22dba4a3e031b40273792bd88fa19d24 100644
--- a/LayoutTests/http/tests/serviceworker/ServiceWorkerGlobalScope/resources/update-worker.php
+++ b/LayoutTests/http/tests/serviceworker/ServiceWorkerGlobalScope/resources/update-worker.php
@@ -1,7 +1,6 @@
 <?php
-// Force the browser to cache this script. update() should always bypass this
-// cache and fetch a new version.
-header('Cache-Control: max-age=86400');
+// Update obeys max-age, so set it to 0 for update() to find a new version.
+header('Cache-Control: max-age=0');

[falken, 2015/09/11 12:35:26]

Can you also test the converse: if the browser caches the script, update() does
not find a new version?

[jungkees, 2015/09/15 12:09:17]

Yes, when the script is served from cache, update() does not find a new version
nor updatefound is fired. I added a test for it.

 
 // Return a different script for each access.
 header('Content-Type:application/javascript');