Bug 811126
| Summary: | Enable PortalRequestHandler to set Cache-control according to some configuration option | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 6 | Reporter: | Adam Kovari <akovari> | |
| Component: | Portal | Assignee: | Nobody <nobody> | |
| Status: | VERIFIED --- | QA Contact: | ||
| Severity: | low | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 6.0.0 | CC: | bdawidow, epp-bugs, jpallich, nobody, ppalaga, theute, tkyjovsk | |
| Target Milestone: | DR01 | |||
| Target Release: | 6.2.0 | |||
| Hardware: | All | |||
| OS: | All | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
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.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1072146 (view as bug list) | Environment: | ||
| Last Closed: | Type: | Feature Request | ||
| 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: | 1072146 | |||
Pull request: https://github.com/gatein/gatein-portal/pull/759 Fixed in GateIn master (3.7.x) I tested setting a custom value for cacheControl portal property via UI. After page reload the server returns the specified value in the "Cache-Control" header. When the portal/site is exported there is an entry for cacheControl in the properties block of portal.xml file. <entry key="cacheControl">VALUE</entry> Note: Any string value is accepted in the cache-control input field. There is no validation. |
Description of problem: org.exoplatform.portal.application.PortalRequestHandler calls res.setHeader("Cache-Control", "no-cache"); need to change "no-cache" to "no-store", "must-revalidate", "max-age=0", ... Version-Release number of selected component (if applicable): EPP 5 How reproducible: always Actual results: the Cache-control setting is harcoded in java code Expected results: pick Cache-control from configuration option Additional info: please request if needed