Page MenuHome

Improving static content serving
Closed, ResolvedPublic


When deploying new versions of Pillar-based web applications, it often happens that static resources (such as CSS) are not served to clients since they are cached from previous sessions.

Some documentation suggests to adopt a hybrid approach, which consists of using:

  • http headers for performance
  • resource naming for cache invalidation

While setting https headers is relatively easy, it remains to be decided which one is the best solution for renaming the resources themselves. For example, main.s7f0gd.css-> main.f89gha.css.