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: