javascript - Is there any way other than caching to avoid the second request of the app manifest? -


when taking page offline, browser (glossing on details) download page, manifest, , resources, , when done re-request manifest (step 24 here), , if gets doesn't match first 1 got, caching fails.

according spec, browser should schedule attempt after "short delay" (step 25). sadly, far can tell, neither chrome nor firefox last part; instead, fail cache (or update) page , don't retry it.

so in order pages reliably cached/updated, need make sure second copy of manifest byte-for-byte copy of first 1 few moments before.

if data page has kind of built-in version can use in manifest, great, if not seems options are:

  1. generate kind of synthetic version , remember on server can return same version 2 requests.

  2. allow browser cache manifest short time (say, 2 minutes) in normal cache; way, second request satisfied browser's normal cache, , byte-for-byte. of course, means can't update page within 2 minutes.

i'm not seeing in spec, there way avoid second manifest load entirely, avoid either option? tell browser point-in-time of first manifest fine, don't want recheck after? (in our case, know sure world won't change half-way through downloading resources, reason second check doesn't apply us.)


Comments

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

java - UML - How would you draw a try catch in a sequence diagram? -

c++ - No viable overloaded operator for references a map -