When i deploy into a site which has aggregation turned on, the CSS/JS aggregation files may be re-created with new content, but the file name remains the same. This makes it difficult to cache bust these files. For this reason, I think this 2 week caching is problematic and would cause issues for people who don't understand the mechanisms and how to address them.
|
rules: |
|
# Provide a longer TTL (2 weeks) for aggregated CSS and JS files. |
|
'^/sites/default/files/(css|js)': |
|
expires: 2w |
More information on this ticket https://www.drupal.org/project/drupal/issues/3370828#comment-15140268
When i deploy into a site which has aggregation turned on, the CSS/JS aggregation files may be re-created with new content, but the file name remains the same. This makes it difficult to cache bust these files. For this reason, I think this 2 week caching is problematic and would cause issues for people who don't understand the mechanisms and how to address them.
drupal9/.platform.app.yaml
Lines 142 to 145 in ae188ba
More information on this ticket https://www.drupal.org/project/drupal/issues/3370828#comment-15140268