a0af552d0f
Prior to this commit, the resource handler serving static resources for Spring MVC and Spring WebFlux would always look at the `Resource#lastModified` information, derive the `"Last-Modified"` HTTP response header and support HTTP conditional requests with that information. In some cases, builds or packaging tools choose to set this last modification date to a static date in the past. This allows tools to have reproducible builds or to leverage caching given the static resources content didn't change. This can lead to problems where this static date (e.g. "1980-01-01") is used literally in HTTP responses and will make the HTTP caching mechanism counter-productive: the content of the resources changed, but the application insists on saying it didn't change since the 80s... This commit adds a new configuration option to disable this support - there is no way to automatically discard those dates: there is no standard for that and many don't use he "EPOCH 0 date" as it can lead to compatibility issues with different OSes. Closes gh-25845 |
||
|---|---|---|
| .. | ||
| integration.adoc | ||
| web-uris.adoc | ||
| webflux-cors.adoc | ||
| webflux-functional.adoc | ||
| webflux-view.adoc | ||
| webflux-webclient.adoc | ||
| webflux-websocket.adoc | ||
| webflux.adoc | ||
| webmvc-client.adoc | ||
| webmvc-cors.adoc | ||
| webmvc-functional.adoc | ||
| webmvc-test.adoc | ||
| webmvc-view.adoc | ||
| webmvc.adoc | ||
| websocket-intro.adoc | ||
| websocket.adoc | ||