Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using last modified for static resources in reproducible archives and images causes unwanted browser caching #24099

Closed
bclozel opened this issue Nov 9, 2020 · 0 comments
Assignees
Milestone

Comments

@bclozel
Copy link
Member

@bclozel bclozel commented Nov 9, 2020

In spring-projects/spring-framework#25845, Spring Framework introduced a new option for serving static resources that enables/disables usage of the last modified file metadata when serving static resources.

As described in the Framework issue, this can lead to problems when applications are packaged as container images and files metadata are changed for caching or reproducibility. Since Spring Boot now builds application as container images using Cloud Native Buildpacks, we should consider this as a bug since Spring Boot users have no way to change that without writing a fair amount of code.

Adding this option will enable developers to switch it on in environments where file metadata is overwritten.

@bclozel bclozel added this to the 2.4.0 milestone Nov 9, 2020
@bclozel bclozel self-assigned this Nov 9, 2020
@wilkinsona wilkinsona changed the title Add spring.web.resources.use-last-modified configuration property Using last modified for static resources in reproducible archives and images causes unwanted browser caching Nov 9, 2020
@bclozel bclozel closed this in f0a6128 Nov 10, 2020
bclozel added a commit that referenced this issue Nov 10, 2020
Polish
See gh-24099
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant