Improving static content serving #53890

New Issue

Francesco Siddi · 2018-01-24T19:27:16+01:00

Francesco Siddi commented

2018-01-24 19:27:16 +01:00

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.

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](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching) 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](https://github.com/h5bp/server-configs-apache/blob/master/dist/.htaccess), it remains to be decided which one is the best solution for renaming the resources themselves. For example, `main.s7f0gd.css`-> `main.f89gha.css`.

Francesco Siddi self-assigned this 2018-01-24 19:27:16 +01:00

Francesco Siddi commented

2018-01-24 19:27:16 +01:00

Added subscribers: @fsiddi, @dr.sybren, @pablovazquez