PRB: CCPKG Does Not Pick Up the Updated Archive File When the Source Script Is Defined by http:// (317954)

SYMPTOMS

The CCPKG utility does not pick up the source script properly when the source script is defined by http://. The utility works properly when the source script is defined by file://.

WORKAROUND

When you create archives from local files, use file:// instead of http:// to avoid caching problems, or mark the pages as non-cacheable. Also, if you plan to change the http:// pages, mark these pages as non-cacheable.

You can make a page non-cacheable by incorporating JScript in the HTML page and by adding a META tag that shows the expiration of the content in the file, as in the following sample code:

<meta http-equiv="expires" content="description">

Later updates to the file overwrite the copy in the cache.

MORE INFORMATION

For a channel with a package script, the package script runs when the package is installed. If you change the script, the archive is re-created, and then the client tries to synchronize the archive with the server. However, the client picks up the old archive from the cache instead of picking up the archive from the server.

Steps to Reproduce the Behavior

Register a channel with a preinstall script that has one echo statement, "Hello World". When the client installs the script, the text "Hello World" appears.
Change the preinstall script so that the text that appears is "Hello everyone". The archive is re-created.
Delete the Configcfg.db file, and then restart the client.