[MAGNOLIA-2315] SetExpirationHeaders sets wrong value Created: 12/Aug/08  Updated: 23/Jan/13  Resolved: 12/Aug/08

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 3.6.1
Fix Version/s: 3.6.2, 3.6.3

Type: Bug Priority: Major
Reporter: Ian Johannesen Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

The expiration is set to +400 months from now even though the requested amount in minutes is 30. This seems to be because System.currentTimeMillis() isn't subtracted - or not factored into the calculations in info.magnolia.module.cache.executor.SetExpirationHeaders:76.

Patch is included with MAGNOLIA-2314



 Comments   
Comment by Magnolia International [ 12/Aug/08 ]

Patch applied, thanks !

Generated at Mon Feb 12 03:35:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.