Nevermind, i finally traced it all the way through the problem lies in the
Spring Framework code. For anyone who happens to trip up on the same
problem, our Spring is doing this in WebContentGenerator.applyCacheControl
if (response.containsHeader(HEADER_EXPIRES)) {
// Reset HTTP 1.0 Expires header if present
response.setHeader(HEADER_EXPIRES, "");
}
On Tue, Jul 9, 2019 at 12:03 PM Tom Kuo <tom....@spiderstrategies.com>
wrote:
> I saw this both on 8.5.0.39 and 9.0.14
>>
>
> Oh actually this was also present on the latest 8.5.42
>
