fietser97 commented on issue #13393: URL: https://github.com/apache/maven/issues/13393#issuecomment-6170871349
> 13\. > I'd be interested to understand precisely what it breaks for you: how do you recognize "the newest version"? > > are you building SNAPSHOTs? or only releases? > > what is "build-info" to you? how do you get visibility into it? > > > Completely different person/use-case here, but I would chime in with a very basic and provable use-case: > > **Spring-boot web apps use the jar's mtime for embedded asset Last-Modified HTTP header value.** Setting the mtime to 1980-02-01 breaks timestamp-based caching protocols completely (when a new software image or jar is published), as all Last-Modified headers sent by the app become 1980-02-01 and thus the browser will think no asset is ever changing when it sends requests with `If-Modified-Since`. > No custom or special setup is needed to produce this problem: just create a simple spring boot web project that serves embedded assets — simple enough. Observe that all assets have `Last-Modified: Fri, 01 Feb 1980 00:00:00 GMT` and are cached unexpectedly as new releases roll out. > > (Note: sure, we could configure Etags or other custom caching protocols, or configure a custom caching logic, but there is no need for those and they just add complexity when time-modified caching was/is working fine.) I hadn't even looked this far into the issue. Good catch. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
