[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Ivan Ravin updated RF-11992: ---------------------------- Workaround Description: The workaround for richfaces 3.3.3 is to set empty pragma for transportHeaders in method org.ajax4jsf.resource.InternetResourceBase.sendHeaders(ResourceContext context): add this string {code:title=org.ajax4jsf.resource.InternetResourceBase.java|borderStyle=solid} ... if (cached) { ... context.setHeader("Pragma", "");//**** this } {code} the same workaround for richfaces 4.x: in method org.richfaces.resource.AbstractCacheableResource.addCacheControlResponseHeaders(...): {code:title=org.richfaces.resource.AbstractCacheableResource.java|borderStyle=solid} ... if (maxAge > 0) { headers.put("Cache-Control", "max-age=" + maxAge); headers.put("Pragma", "");//**** this } {code} For GateIn this patch is enough, JBoss portal 2.7.2 requires some additional work to pach portal code. There is 2 methods sendBinary(...) in org.jboss.portal.core.controller.handler.HTTPResponse.java to patch: {code:title=org.jboss.portal.core.controller.handler.HTTPResponse.java|borderStyle=solid} ... if (properties != null) { for (String key: properties.keySet()) { if (properties.getValue(key) != null) { resp.setHeader(key, properties.getValue(key)); //**** instead addHeader(...) } } } {code} was: The workaround for richfaces 3.3.3 is to set empty pragma for transportHeaders in method org.ajax4jsf.resource.InternetResourceBase.sendHeaders(ResourceContext context): add this string {code:title=org.ajax4jsf.resource.InternetResourceBase.java|borderStyle=solid} ... if (cached) { ... context.setHeader("Pragma", "");//**** this } {code} the same workaround for richfaces 4.1: in method org.richfaces.resource.AbstractCacheableResource.addCacheControlResponseHeaders(...): {code:title=org.richfaces.resource.AbstractCacheableResource.java|borderStyle=solid} ... if (maxAge > 0) { headers.put("Cache-Control", "max-age=" + maxAge); headers.put("Pragma", "");//**** this } {code} For GateIn this patch is enough, JBoss portal 2.7.2 requires some additional work to pach portal code. There is 2 methods sendBinary(...) in org.jboss.portal.core.controller.handler.HTTPResponse.java to patch: {code:title=org.jboss.portal.core.controller.handler.HTTPResponse.java|borderStyle=solid} ... if (properties != null) { for (String key: properties.keySet()) { if (properties.getValue(key) != null) { resp.setHeader(key, properties.getValue(key)); //**** instead addHeader(...) } } } {code} Priority: Minor (was: Major) Forum Reference: https://community.jboss.org/thread/178136?tstart=150 (was: https://community.jboss.org/thread/178136?tstart=150) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Ivan Ravin updated RF-11992: ---------------------------- Description: On Jboss and Gatein portal richfaces cant be cached when user is logged in. Bug is found for richfaces 3.3.3 but i think can be reproduced for 4.x because org.richfaces.resource.AbstractCacheableResource has similar code. The steps for reproduce bug are: download portlet bridge 2.2 archive deploy richFacesPortlet.war from portlet bridge archive (i used jboss portal 2.7.2 bundle and GateIn-3.1.0-FINAL-jbossas) look at network activity (i did with firefox + firebug, the same result on any other browser). Just open page with richfaces portlet. When user is not logged in, all richfaces resources are caching well, and this is headers returned by server: |Cache-Control |max-age=86400| |Content-Type |text/javascript| |Date |Thu, 26 Jan 2012 17:57:39 GMT| |Expires |27 Jan 2012 17:57:39 GMT| |Last-Modified |26 Jan 2012 17:42:17 GMT| |Server |Apache-Coyote/1.1| |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| But when user is logged in all richfaces stuff come from network every time (more than 1.3 mb). This is headers returned by portal 2.7.2 when user logged in: |Cache-Control |{color:red}no-cache,{color} max-age=86400| |Content-Type |text/javascript| |Date |Thu, 26 Jan 2012 18:26:49 GMT| |Expires |{color:red}Thu, 01 Jan 1970 03:00:00 MSK,{color} 27 Jan 2012 18:26:49 GMT| |Last-Modified |26 Jan 2012 18:05:56 GMT| |{color:red}Pragma{color} |{color:red}No-cache{color}| |Server |Apache-Coyote/1.1| |Transfer-Encoding |chunked| |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| The same problem with GateIn-3.1.0-FINAL-jbossas bundle, but now only one wrong header: |Cache-Control |max-age=86400| |Content-Type |text/javascript;charset=UTF-8| |Date |Sat, 28 Jan 2012 08:54:14 GMT| |Expires |29 Jan 2012 08:54:14 GMT| |Last-Modified |28 Jan 2012 08:51:11 GMT| |{color:red}Pragma{color} |{color:red}No-cache{color}| |Server |Apache-Coyote/1.1| |Transfer-Encoding |chunked| |X-Powered-By |Servlet 2.5; JBoss-5.0/JBossWeb-2.1| This header (Pragma) appears only when user is logged in, and again, all richfaces resources come through network. I did some debug and found that richfaces create good headers, but there is some code in portal which put wrong values into real response before richfaces. I cant find this code in portal sources, so maybe it is JBoss AS problem, or third party component. In Gatein portal problem was partially resolved: it overwrites 2 wrong headers with values provided by richfaces, but "pragma" header is absent in richfaces response, and this way in secured portlets richfaces generate too much unnesessary traffic. To solve problem for GateIn there is enough to provide empty Pragma header; To solve problem for JBoss Portal its required to fix resource processing like it done in gatein. was: On Jboss and Gatein portal richfaces cant be cached when user is logged in. Bug is found for richfaces 3.3.3 but i think can be reproduced for 4.x because org.richfaces.resource.AbstractCacheableResource has similar code. The steps for reproduce bug are: download portlet bridge 2.2 archive deploy richFacesPortlet.war from portlet bridge archive (i used jboss portal 2.7.2 bundle and GateIn-3.1.0-FINAL-jbossas) look at network activity (i did with firefox + firebug, the same result on any other browser). Just open page with richfaces portlet. When user is not logged in, all richfaces resources are caching well, and this is headers returned by server: |Cache-Control |max-age=86400| |Content-Type |text/javascript| |Date |Thu, 26 Jan 2012 17:57:39 GMT| |Expires |27 Jan 2012 17:57:39 GMT| |Last-Modified |26 Jan 2012 17:42:17 GMT| |Server |Apache-Coyote/1.1| |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| But when user is logged in all richfaces stuff come from network every time (more than 1.3 mb). This is headers returned by portal 2.7.2 when user logged in: |Cache-Control |{color:red}no-cache,{color} max-age=86400| |Content-Type |text/javascript| |Date |Thu, 26 Jan 2012 18:26:49 GMT| |Expires |{color:red}Thu, 01 Jan 1970 03:00:00 MSK,{color} 27 Jan 2012 18:26:49 GMT| |Last-Modified |26 Jan 2012 18:05:56 GMT| |{color:red}Pragma{color} |{color:red}No-cache{color}| |Server |Apache-Coyote/1.1| |Transfer-Encoding |chunked| |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| The same problem with GateIn-3.1.0-FINAL-jbossas bundle, but now only one wrong header: |Cache-Control |max-age=86400| |Content-Type |text/javascript;charset=UTF-8| |Date |Sat, 28 Jan 2012 08:54:14 GMT| |Expires |29 Jan 2012 08:54:14 GMT| |Last-Modified |28 Jan 2012 08:51:11 GMT| |{color:red}Pragma{color} |{color:red}No-cache{color}| |Server |Apache-Coyote/1.1| |Transfer-Encoding |chunked| |X-Powered-By |Servlet 2.5; JBoss-5.0/JBossWeb-2.1| This header (Pragma) appears only when user is logged in, and again, all richfaces resources come through network. I did some debug and found that richfaces create good headers, but there is some code in portal which put wrong values into real response before richfaces. I cant find this code in portal sources, so maybe it is JBoss AS problem, or third party component. Gatein portal overwrite 2 wrong headers with values provided by richfaces, but "pragma" header is absent in richfaces response, and this way in secured portlets richfaces generate too much unnesessary traffic. Forum Reference: https://community.jboss.org/thread/178136?tstart=150 (was: https://community.jboss.org/thread/178136?tstart=150) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Ivan Ravin updated RF-11992: ---------------------------- Workaround Description: The workaround for richfaces 3.3.3 is to set empty pragma for transportHeaders in method org.ajax4jsf.resource.InternetResourceBase.sendHeaders(ResourceContext context): add this string {code:title=org.ajax4jsf.resource.InternetResourceBase.java|borderStyle=solid} ... if (cached) { ... context.setHeader("Pragma", "");//**** this } {code} the same workaround for richfaces 4.x: in method org.richfaces.resource.AbstractCacheableResource.addCacheControlResponseHeaders(...): {code:title=org.richfaces.resource.AbstractCacheableResource.java|borderStyle=solid} ... if (maxAge > 0) { headers.put("Cache-Control", "max-age=" + maxAge); headers.put("Pragma", "");//**** this } {code} For GateIn this patch is enough, JBoss portal 2.7.2 requires some additional work to pach portal code. There is 2 methods sendBinary(...) in org.jboss.portal.core.controller.handler.HTTPResponse.java where must be setHeader instead addHeader: {code:title=org.jboss.portal.core.controller.handler.HTTPResponse.java|borderStyle=solid} ... if (properties != null) { for (String key: properties.keySet()) { if (properties.getValue(key) != null) { resp.setHeader(key, properties.getValue(key)); //**** instead addHeader(...) } } } {code} was: The workaround for richfaces 3.3.3 is to set empty pragma for transportHeaders in method org.ajax4jsf.resource.InternetResourceBase.sendHeaders(ResourceContext context): add this string {code:title=org.ajax4jsf.resource.InternetResourceBase.java|borderStyle=solid} ... if (cached) { ... context.setHeader("Pragma", "");//**** this } {code} the same workaround for richfaces 4.x: in method org.richfaces.resource.AbstractCacheableResource.addCacheControlResponseHeaders(...): {code:title=org.richfaces.resource.AbstractCacheableResource.java|borderStyle=solid} ... if (maxAge > 0) { headers.put("Cache-Control", "max-age=" + maxAge); headers.put("Pragma", "");//**** this } {code} For GateIn this patch is enough, JBoss portal 2.7.2 requires some additional work to pach portal code. There is 2 methods sendBinary(...) in org.jboss.portal.core.controller.handler.HTTPResponse.java to patch: {code:title=org.jboss.portal.core.controller.handler.HTTPResponse.java|borderStyle=solid} ... if (properties != null) { for (String key: properties.keySet()) { if (properties.getValue(key) != null) { resp.setHeader(key, properties.getValue(key)); //**** instead addHeader(...) } } } {code} Forum Reference: https://community.jboss.org/thread/178136?tstart=150 (was: https://community.jboss.org/thread/178136?tstart=150) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Ivan Ravin updated RF-11992: ---------------------------- Description: On Jboss and Gatein portal richfaces cant be cached when user is logged in. Bug is found for richfaces 3.3.3 but i think can be reproduced for 4.x because org.richfaces.resource.AbstractCacheableResource has similar code. The steps for reproduce bug are: download portlet bridge 2.2 archive deploy richFacesPortlet.war from portlet bridge archive (i used jboss portal 2.7.2 bundle and GateIn-3.1.0-FINAL-jbossas) look at network activity (i did with firefox + firebug, the same result on any other browser). Just open page with richfaces portlet. When user is not logged in, all richfaces resources are caching well, and this is headers returned by server: |Cache-Control |max-age=86400| |Content-Type |text/javascript| |Date |Thu, 26 Jan 2012 17:57:39 GMT| |Expires |27 Jan 2012 17:57:39 GMT| |Last-Modified |26 Jan 2012 17:42:17 GMT| |Server |Apache-Coyote/1.1| |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| But when user is logged in all richfaces stuff come from network every time (more than 1.3 mb). This is headers returned by portal 2.7.2 when user logged in: |Cache-Control |{color:red}no-cache,{color} max-age=86400| |Content-Type |text/javascript| |Date |Thu, 26 Jan 2012 18:26:49 GMT| |Expires |{color:red}Thu, 01 Jan 1970 03:00:00 MSK,{color} 27 Jan 2012 18:26:49 GMT| |Last-Modified |26 Jan 2012 18:05:56 GMT| |{color:red}Pragma{color} |{color:red}No-cache{color}| |Server |Apache-Coyote/1.1| |Transfer-Encoding |chunked| |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| The same problem with GateIn-3.1.0-FINAL-jbossas bundle, but now only one wrong header: |Cache-Control |max-age=86400| |Content-Type |text/javascript;charset=UTF-8| |Date |Sat, 28 Jan 2012 08:54:14 GMT| |Expires |29 Jan 2012 08:54:14 GMT| |Last-Modified |28 Jan 2012 08:51:11 GMT| |{color:red}Pragma{color} |{color:red}No-cache{color}| |Server |Apache-Coyote/1.1| |Transfer-Encoding |chunked| |X-Powered-By |Servlet 2.5; JBoss-5.0/JBossWeb-2.1| This header (Pragma) appears only when user is logged in, and again, all richfaces resources come through network. I did some debug and found that richfaces create good headers, but there is some code in portal which put wrong values into real response before richfaces. I cant find this code in portal sources, so maybe it is JBoss AS problem, or third party component. In Gatein portal problem was partially resolved: it overwrites 2 wrong headers with values provided by richfaces, but "pragma" header is absent in richfaces response, and this way in secured portlets richfaces generate too much unnesessary traffic. To solve problem for GateIn there is enough to provide empty Pragma header; To solve problem for JBoss Portal its required to fix resource headers processing in portal code, like it done in gatein. was: On Jboss and Gatein portal richfaces cant be cached when user is logged in. Bug is found for richfaces 3.3.3 but i think can be reproduced for 4.x because org.richfaces.resource.AbstractCacheableResource has similar code. The steps for reproduce bug are: download portlet bridge 2.2 archive deploy richFacesPortlet.war from portlet bridge archive (i used jboss portal 2.7.2 bundle and GateIn-3.1.0-FINAL-jbossas) look at network activity (i did with firefox + firebug, the same result on any other browser). Just open page with richfaces portlet. When user is not logged in, all richfaces resources are caching well, and this is headers returned by server: |Cache-Control |max-age=86400| |Content-Type |text/javascript| |Date |Thu, 26 Jan 2012 17:57:39 GMT| |Expires |27 Jan 2012 17:57:39 GMT| |Last-Modified |26 Jan 2012 17:42:17 GMT| |Server |Apache-Coyote/1.1| |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| But when user is logged in all richfaces stuff come from network every time (more than 1.3 mb). This is headers returned by portal 2.7.2 when user logged in: |Cache-Control |{color:red}no-cache,{color} max-age=86400| |Content-Type |text/javascript| |Date |Thu, 26 Jan 2012 18:26:49 GMT| |Expires |{color:red}Thu, 01 Jan 1970 03:00:00 MSK,{color} 27 Jan 2012 18:26:49 GMT| |Last-Modified |26 Jan 2012 18:05:56 GMT| |{color:red}Pragma{color} |{color:red}No-cache{color}| |Server |Apache-Coyote/1.1| |Transfer-Encoding |chunked| |X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0| The same problem with GateIn-3.1.0-FINAL-jbossas bundle, but now only one wrong header: |Cache-Control |max-age=86400| |Content-Type |text/javascript;charset=UTF-8| |Date |Sat, 28 Jan 2012 08:54:14 GMT| |Expires |29 Jan 2012 08:54:14 GMT| |Last-Modified |28 Jan 2012 08:51:11 GMT| |{color:red}Pragma{color} |{color:red}No-cache{color}| |Server |Apache-Coyote/1.1| |Transfer-Encoding |chunked| |X-Powered-By |Servlet 2.5; JBoss-5.0/JBossWeb-2.1| This header (Pragma) appears only when user is logged in, and again, all richfaces resources come through network. I did some debug and found that richfaces create good headers, but there is some code in portal which put wrong values into real response before richfaces. I cant find this code in portal sources, so maybe it is JBoss AS problem, or third party component. In Gatein portal problem was partially resolved: it overwrites 2 wrong headers with values provided by richfaces, but "pragma" header is absent in richfaces response, and this way in secured portlets richfaces generate too much unnesessary traffic. To solve problem for GateIn there is enough to provide empty Pragma header; To solve problem for JBoss Portal its required to fix resource processing in portal code, like it done in gatein. Forum Reference: https://community.jboss.org/thread/178136?tstart=150 (was: https://community.jboss.org/thread/178136?tstart=150) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Ivan Ravin commented on RF-11992: --------------------------------- Portlet bridge does nothing with headers, so this bug "distributed" between portal and richfaces. I think it's rather portal bug (and it was partially fixed in GateIn), but suggested fix for richfaces by reason of symmetry: for non cached resources richfaces provide legacy Pragma header, but for cached does not: {code:title=org.ajax4jsf.resource.InternetResourceBase.java(3.3.3)|borderStyle=solid} ... if (cached) { ... context.setDateHeader("Expires", System.currentTimeMillis() + expired); context.setHeader("Cache-control", "max-age=" + (expired / 1000L)); context.setHeader("Pragma", "");//<-- suggestion } else { ... context.setHeader("Cache-control", "max-age=0, no-store, no-cache"); context.setHeader("Pragma", "no-cache"); context.setIntHeader("Expires", 0); } {code} The same "symmetry" reason for richfaces 4.x: org.richfaces.resource.AbstractBaseResource provides Pragma header in method addNoCacheResponseHeaders(), but org.richfaces.resource.AbstractCacheableResource does not provide it in method addCacheControlResponseHeaders() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11992: ------------------------------- Fix Version/s: 4.3.0.Milestone1 Forum Reference: https://community.jboss.org/thread/178136?tstart=150 (was: https://community.jboss.org/thread/178136?tstart=150) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11992: ------------------------------- Fix Version/s: 4.3.0.Milestone2 (was: 4.3.0.Milestone1) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11992: ------------------------------- Fix Version/s: (was: 4.3.0.Milestone2) Forum Reference: https://community.jboss.org/thread/178136?tstart=150 (was: https://community.jboss.org/thread/178136?tstart=150) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Lincoln Baxter III commented on RF-11992: ----------------------------------------- But hacking in an extra Pragma header line just to solve this one scenario is not the right solution (most likely.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11992: ------------------------------- Labels: waiting_on_user (was: ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11992: ------------------------------- Labels: (was: waiting_on_user) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-11992: ------------------------------------ Thanks for the clear interpretation of what's going on Ivan. As I understand it, the Portal Bridge is seeding the headers map with key-value pairs: {quote} "Pragma" -> "no-cache" "Cache-Control" -> "no-cache" {quote} RichFaces then sets the _Cache-Control_ header for the cacheable resource, overiding the value seeded by the Portal Bridge, but this leaves the conflicting _Pragma_ un-changed. To be correct in how we deal with this, it seems RichFaces should remove the _Pragma_ value from the _headers_ map, rather than set it to an empty value, as in: {code} if ("no-cache".equalsIgnoreCase(headers.get("Pragma"))) { headers.remove("Pragma"); } {code} If this seems reasonable (and works!), then we'll go ahead with this solution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11992: ------------------------------- Sprint: 4.3.0.M2 - Final Sprint -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Ivan Ravin commented on RF-11992: --------------------------------- Brian, your solution does nothing with real response, because in portal environment richfaces works with copy of headers map. You remove wrong key/value from copy, but in real headers map it still persists. This is code from org.exoplatform.portal.application.PortalRequestContext where headers key/values finally falls: {code:title=org.exoplatform.portal.application.PortalRequestContext.java|borderStyle=solid} ... // in this case headers is map from AbstractCacheableResource, without Pragma header, // and response_ is real HttpServletResponse, where Pragma no-cache already set public void setHeaders(Map<String, String> headers) { Set<String> keys = headers.keySet(); for (Iterator<String> iter = keys.iterator(); iter.hasNext();) { String key = iter.next(); response_.setHeader(key, headers.get(key)); } } {code} As you can see, this does nothing with Pragma no-cache when this header not present in RF response and already present in real response. My suggestion was to put empty Pragma header to RF response. Your solution will work only if we'll make same changes not only in RF, but in portal code too. In Jboss Portal 2.7.2 situation is worst, and even my solution will not work: {code:title=org.jboss.portal.core.controller.handler.HTTPResponse.java|borderStyle=solid} ... if (properties != null) { for (String key: properties.keySet()) { if (properties.getValue(key) != null) { resp.addHeader(key, properties.getValue(key)); //!!!! :( } } } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Ken Finnigan commented on RF-11992: ----------------------------------- I just tested with GateIn 3.5.0.Beta2 and while logged in as Root on GateIn, there is no Pragma header being set in response, so suggested fix would not work as there is nothing to remove. As far as I can see there is now only cache-control: no-cache being set in header for request and response -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11992?page=com.atlassian.jira.plugin.s... ] Ken Finnigan commented on RF-11992: ----------------------------------- Ivan, Are you saying that with Brians fix in RichFaces it now works, or without Brians fix it works? If the latter, then I suspect something has obviously changed in GateIn to handle the headers differently than the previous versions. Ken -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira