[jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1951) CMS Portlet Window Last-Modified HTTP Header

[Sohil Shah (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBPORTAL-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sohil Shah resolved JBPORTAL-1951.
----------------------------------

    Resolution: Rejected


This approach for using last-modified-header for caching a Portal Page based on the state of just the CMS Window will technically not work

This assumes only a single CMS WIndow is present on the Page, but in reality there could be multiple Windows for other Portlets including other CMS Windows on the same page.

Calculating last-modified-header value for such a Page is impossible.

In a nutshell, its not possible to cache dynamic content and produce consistent results

Last-Modified-Header for binary resources served up by the CMS is of course feasible and fixed in an earlier task referenced on this issue

> CMS Portlet Window Last-Modified HTTP Header
> --------------------------------------------
>
>                 Key: JBPORTAL-1951
>                 URL: https://jira.jboss.org/jira/browse/JBPORTAL-1951
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6 Final, 2.6.1 Final, 2.6.2 Final, 2.6.3 Final, 2.6.4 Final
>            Reporter: Mike Millson
>            Assignee: Sohil Shah
>             Fix For: 2.6.6 Final
>
>
> Add the HTTP last-modified header to the CMS Portlet Window. Currently CMS page links (images, css, js) do have the last-modified header set; however, the main page does not.
> Perhaps change the CMSPortlet to outject the header info so it can be injected during final page rendering.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira