539099 - Jetpack should properly handle cached scripts when trying to update an installed feature

Status: RESOLVED WONTFIX

(Mozilla Labs :: Jetpack Prototype, defect)

Description

[(no longer active)]

What currently happens is that if the browser cache contains a jetpack, next time that jetpack tries to update it, it just grabs the version of the script which is residing in the cache (and is therefore the old version) and does not query the server for a newer version.

Jetpack should fix this by actually sending an HTTP header and only reading from the cache if the server replies with HTTP 304 status, like any other web client.  Unless this is fixed, webmasters have to configure their browser to send headers such as |Cache-Control: private| so that the script won't be cached at all.

Comment 1

[Daniel Buchner [:dbuc]]

We will be monitoring all these issues after the rebooted Jetpack code base is released in the first week of March to ensure their causes are not duplicated. Many of the bugs/issues with the prototype version of Jetpack will be made irrelevant given the structure of the new SDK.