11:05 a.m.
Lukáš Fryč created RF-11890:
-------------------------------
Summary: ResourceServlet does not set HTTP headers for caching
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Assignee: Lukáš Fryč
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
2:33 a.m.
[
https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-11890:
---------------------------------
Check also that regular RichFaces resources have headers setup properly when resource
mapping is off.
ResourceServlet does not set HTTP headers for caching
-----------------------------------------------------
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Assignee: Lukáš Fryč
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
2:09 p.m.
[
https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-11890:
---------------------------------
Even though headers are not set for resources server by ResourceServlet,
caching works on browser side out of the box,
verified on RichFaces Showcase hosting http://showcase.richfaces.org/
ResourceServlet does not set HTTP headers for caching
-----------------------------------------------------
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Assignee: Lukáš Fryč
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
2:09 p.m.
[
https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč reassigned RF-11890:
-------------------------------
Assignee: (was: Lukáš Fryč)
ResourceServlet does not set HTTP headers for caching
-----------------------------------------------------
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
2:09 p.m.
[
https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč updated RF-11890:
----------------------------
Comment: was deleted
(was: Check also that regular RichFaces resources have headers setup properly when
resource mapping is off.)
ResourceServlet does not set HTTP headers for caching
-----------------------------------------------------
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
10:37 a.m.
[
https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11890:
-------------------------------
Assignee: Lukáš Fryč
Forum Reference: https://community.jboss.org/message/646969#646969 (was:
https://community.jboss.org/message/646969#646969)
Lukas, I thought we discussed this issue, and found it to be the result of a local setting
in your browser?
ResourceServlet does not set HTTP headers for caching
-----------------------------------------------------
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Assignee: Lukáš Fryč
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
2:51 a.m.
[
https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-11890:
---------------------------------
True is that these resources are cached by browsers implicitly, but we could improve that
by explicitly adding caching settings. More investigations in that space may be necessary
to determine how serious the issues is.
ResourceServlet does not set HTTP headers for caching
-----------------------------------------------------
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Assignee: Lukáš Fryč
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
8:36 a.m.
New subject: [JBoss JIRA] (RF-11890) Provider HTTP cache-expires headers for ResourceServlet resources
[
https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč updated RF-11890:
----------------------------
Summary: Provider HTTP cache-expires headers for ResourceServlet resources
(was: ResourceServlet does not set HTTP headers for caching)
Issue Type: Feature Request (was: Bug)
Fix Version/s: 4.3-Tracking
Forum Reference: https://community.jboss.org/message/646969#646969 (was:
https://community.jboss.org/message/646969#646969)
Provider HTTP cache-expires headers for ResourceServlet resources
-----------------------------------------------------------------
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Assignee: Lukáš Fryč
Fix For: 4.3-Tracking
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
8:36 a.m.
New subject: [JBoss JIRA] (RF-11890) Provider HTTP cache-expires headers for ResourceServlet resources
[
https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč reassigned RF-11890:
-------------------------------
Assignee: (was: Lukáš Fryč)
Provider HTTP cache-expires headers for ResourceServlet resources
-----------------------------------------------------------------
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Fix For: 4.3-Tracking
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
8:36 a.m.
New subject: [JBoss JIRA] (RF-11890) Provide HTTP cache-expires headers for ResourceServlet resources
[
https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč updated RF-11890:
----------------------------
Summary: Provide HTTP cache-expires headers for ResourceServlet resources
(was: Provider HTTP cache-expires headers for ResourceServlet resources)
Forum Reference: https://community.jboss.org/message/646969#646969 (was:
https://community.jboss.org/message/646969#646969)
Provide HTTP cache-expires headers for ResourceServlet resources
----------------------------------------------------------------
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Fix For: 4.3-Tracking
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
2:43 p.m.
New subject: [JBoss JIRA] (RF-11890) Provide HTTP cache-expires headers for ResourceServlet resources
[
https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-11890:
---------------------------------
http://www.stevesouders.com/blog/2012/03/22/cache-them-if-you-can/?utm_so...
Provide HTTP cache-expires headers for ResourceServlet resources
----------------------------------------------------------------
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Fix For: 4.3-Tracking
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
2:45 p.m.
New subject: [JBoss JIRA] (RF-11890) Provide HTTP cache-expires headers for ResourceServlet resources
[
https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-11890:
---------------------------------
Related: RF-9345
Provide HTTP cache-expires headers for ResourceServlet resources
----------------------------------------------------------------
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Fix For: 4.3-Tracking
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
2:45 p.m.
New subject: [JBoss JIRA] (RF-11890) Provide HTTP cache-expires headers for ResourceServlet resources
[
https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-11890 at 5/1/12 3:43 PM:
---------------------------------------------------------
[Cache them if you
can|http://www.stevesouders.com/blog/2012/03/22/cache-them-if-you-can/?ut...]
was (Author: lfryc):
http://www.stevesouders.com/blog/2012/03/22/cache-them-if-you-can/?utm_so...
Provide HTTP cache-expires headers for ResourceServlet resources
----------------------------------------------------------------
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Fix For: 4.3-Tracking
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
2:45 p.m.
New subject: [JBoss JIRA] (RF-11890) Provide HTTP cache-expires headers for ResourceServlet resources
[
https://issues.jboss.org/browse/RF-11890?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-11890 at 5/1/12 3:43 PM:
---------------------------------------------------------
[Cache them if you
can|http://www.stevesouders.com/blog/2012/03/22/cache-them-if-you-can/?ut...]
article
was (Author: lfryc):
[Cache them if you
can|http://www.stevesouders.com/blog/2012/03/22/cache-them-if-you-can/?ut...]
Provide HTTP cache-expires headers for ResourceServlet resources
----------------------------------------------------------------
Key: RF-11890
URL: https://issues.jboss.org/browse/RF-11890
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Fix For: 4.3-Tracking
{quote}
All RichFaces resources served by Faces Servlet have headers set appropriately for
caching.
(You can check it by removing your Filter and turning resourceMapping=false).
I assume you have problems with ResourceServlet where resources does not go through
RichFaces ResourceHandler, so headers are set as for any other JSF resource - which means
(AFAIK) no caching at all.
{quote}
This assumption needs to be verified before implementing.
--
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
4596
days inactive
4702
days old
richfaces-issues@lists.jboss.org
13 comments
2 participants
participants (2)
-
Brian Leathem (JIRA) -
Lukáš Fryč (JIRA)