Back to bug 811126

Who When What Removed Added
Adam Kovari 2012-04-10 08:36:03 UTC Type Bug Feature Request
hfnukal 2012-06-06 12:38:14 UTC Target Release --- 6.0.0.GA
CC hfnukal
Component Portal Portal
Version TBD_EPP_5 6.0.0.GA
Product JBoss Enterprise Portal Platform 5 JBoss Enterprise Portal Platform 6
mark yarborough 2012-09-11 12:28:28 UTC Target Release 6.0.0.GA 6.0.0
Target Milestone --- GA
Jiri Pallich 2013-09-13 12:57:40 UTC Target Release 6.0.0 6.2.0
CC jpallich
Divya Mehra 2013-12-17 16:35:11 UTC CC dmehra
Boleslaw Dawidowicz 2014-01-09 10:29:33 UTC Status NEW ASSIGNED
CC bdawidow
Assignee jbpapp-maint jcosta
Juraci Paixão Kröhling 2014-01-10 14:29:39 UTC Link ID JBoss Issue Tracker GTNPORTAL-3361
Peter Palaga 2014-01-15 19:39:12 UTC Status ASSIGNED POST
CC ppalaga
Target Milestone GA DR01
Thomas Heute 2014-02-03 09:28:52 UTC CC theute
Jared MORGAN 2014-03-04 03:52:36 UTC Blocks 1072146
Peter Palaga 2014-04-04 21:26:53 UTC Status POST MODIFIED
Boleslaw Dawidowicz 2014-04-29 10:24:26 UTC Status MODIFIED ON_QA
Tomas Kyjovsky 2014-05-26 12:56:28 UTC Status ON_QA VERIFIED
CC tkyjovsk
Juraci Paixão Kröhling 2014-07-03 10:09:35 UTC Doc Text Cause:
Cache control cannot be fine tuned.

Consequence:
Highly concurrent portals cannot benefit from caching.

Fix:
Added an option for an administrator to set a custom cache-control string on the portal's configuration.

Result:
An administrator can now fine tune the cache-control HTTP header, based on the portal's needs. Portals without such requirement have the same behavior as before.
Jared MORGAN 2014-07-04 04:42:28 UTC Doc Text Cause:
Cache control cannot be fine tuned.

Consequence:
Highly concurrent portals cannot benefit from caching.

Fix:
Added an option for an administrator to set a custom cache-control string on the portal's configuration.

Result:
An administrator can now fine tune the cache-control HTTP header, based on the portal's needs. Portals without such requirement have the same behavior as before.
Previously, cache control could not be fine tuned. This prevented highly concurrent portals benefiting from caching. The fix adds an option for an administrator to set a custom cache-control string on the portal's configuration. This allows an administrator to fine tune the cache-control HTTP header, based on the portal's needs. Portals without this requirement continue to have the same behavior as before.
Jared MORGAN 2014-07-22 00:17:39 UTC Doc Text Previously, cache control could not be fine tuned. This prevented highly concurrent portals benefiting from caching. The fix adds an option for an administrator to set a custom cache-control string on the portal's configuration. This allows an administrator to fine tune the cache-control HTTP header, based on the portal's needs. Portals without this requirement continue to have the same behavior as before. Previously, cache control could not be fine tuned. This prevented highly concurrent portals benefiting from caching. The enhancement adds an option for an administrator to set a custom cache-control string on the portal's configuration. This allows an administrator to fine tune the cache-control HTTP header, based on the portal's requirements. Portals without this requirement continue to have the same behavior as before.
Doc Type Bug Fix Enhancement
Anurag 2014-11-18 09:22:49 UTC CC adebnath
John Skeoch 2015-09-01 03:04:34 UTC CC nobody
John Skeoch 2016-10-30 22:59:10 UTC CC adebnath
PnT Account Manager 2018-01-30 01:42:13 UTC CC dmehra
PnT Account Manager 2018-02-06 19:19:26 UTC CC hfnukal
Red Hat Bugzilla 2021-11-14 22:29:42 UTC Assignee jcosta nobody

Back to bug 811126