[richfaces-issues] [JBoss JIRA] Closed: (RF-1021) Caching not working for internet resources on Firefox + secure web app

Sat Mar 29 10:32:40 EDT 2008

     [ http://jira.jboss.com/jira/browse/RF-1021?page=all ]

Tsikhon Kuprevich closed RF-1021.
---------------------------------


> Caching not working for internet resources on Firefox + secure web app
> ----------------------------------------------------------------------
>
>                 Key: RF-1021
>                 URL: http://jira.jboss.com/jira/browse/RF-1021
>             Project: RichFaces
>          Issue Type: Feature Request
>    Affects Versions: 3.1.0
>         Environment: JSF-RI 1.2p02, Seam 2.0.0.CR1, JBoss 4.0.3+Tomcat 5.5 (patched to JSF 1.2)
>            Reporter: Jason Anderson
>         Assigned To: Tsikhon Kuprevich
>             Fix For: 3.2.0
>
>
> All internet resources being returned by RichFaces/ajax4jsf (e.g.  /a4j*/*.jsf)  have a custom response header set (e.g. max-age=....).
> For secure applications using SSL, Tomcat automatically tries to set Pragma: no-cache on everything, so you have to write a custom servlet filter for the rest of the application that overrides the no-cache, and sets the cache settings to "public" etc. for resources which are truely static.
> The problem is that the custom filter cannot override resources returned by RichFaces (doesn't seem to matter where in the filter chain the custom filter is, calling response.setHeader will not override the one set in InternetResourceBase.sendHeader ).
> The effect of this is that we can get resources caching correctly in IE, but for Firefox what Richfaces return is incomplete and Firefox refuses to cache any of the RichFaces resources.
> I'm not sure what to recommend, either to allow web app to optionally turn off InternetResourceBase.sendHeaders  and allow application to control this itself, or to simply fix the InternerResourceBase to setup addition response header cache control items like "PUBLIC" or "must-revalidate".

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