Bug 106153
| Summary: | Incorrect calculation of cache expiry times | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Enterprise CMS | Reporter: | Daniel Berrangé <berrange> |
| Component: | other | Assignee: | ccm-bugs-list |
| Status: | CLOSED RAWHIDE | QA Contact: | Jon Orris <jorris> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-12-10 16:39:35 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 100952 | ||
fixed at 37573 |
From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020829 Description of problem: The original code for calculating content item cache expiry time basically just used the lifecycle expiry date. So if an item is scheduled to be live for 6 months, then the expiry is set to 6 months. This caused great pain for authors when they needed to edit & republish an item. Thus ItemDispatcher was changed to do: minimum(default expiry, lifecycle expiry). Unfortunately, ContentSectionServlet has reverted to using the original method of calculating expiry times. This is fixed in test-packaging in p4 36693, but needs to be ported to Troika. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Publish an item, with a lifecycle ending in 6 months 2. Request the item 3. look at the expiry time. Additional info: