Description

Actually mapstore do not send cache headers to the client, but only etags.
Etags is defined weak caching, delegating the client the re-check.
The cache management works well with cache busting using hashes for js, css files.
Anyway for:

• root path (/mapstore/)
• html files (embedded.html)
• json files configuration (e.g. /mapstore/)
• txt files (e.g. version.txt)

These files may need to be revalidated everytime, or the browser (or an intermediate proxy) may decide to cache them for several hours or time.

In order to do so, we have to provide the Cache-Control, Pragma and Expires headers

References:

• Ref 1
• Ref 2