[
https://jira.jboss.org/jira/browse/JBSEAM-4186?page=com.atlassian.jira.pl...
]
Christian Bauer updated JBSEAM-4186:
------------------------------------
Component/s: Core
Remoting
(was: Wiki)
Testing done on wiki, now finishing implementations for conditional GET/HEAD, gzip content
encoding, cache control headers. Still need to actually use them then on improving various
built-in Seam resources.
HTTP caching for SeamResourceServlet resources
----------------------------------------------
Key: JBSEAM-4186
URL:
https://jira.jboss.org/jira/browse/JBSEAM-4186
Project: Seam
Issue Type: Feature Request
Components: Core, Remoting
Reporter: Christian Bauer
Assignee: Christian Bauer
Priority: Critical
Fix For: 2.2.1.CR1
This affects built-in Seam stuff like the remote.js that is always delivered with 200 OK
and can be quite large. We need to explore how/when we can send 304.
I've assigned this to the 'wiki' component because I want to try different
solutions there first.
--
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