Hi the ajax cache control as such is not part of the spec afair. But
normally you can assume that only dynamic data is served hence the
no-cache. (This is just a guess from me)
The easiest way to enable caching might be over a servlet filter or a
custom from the standard JSF Servlet derived from the standard servlet.
Outside of that you probably can plug in your own PartialViewContextImpl
one way or the other (which probably will be harder)
Turning off caching for all ajax is a bad idea, but you might be able to
turn it off selectively with whatever you do by passing down a custom
parameter which then enables your overrides.
Werner
Am 03.04.12 10:12, schrieb Thomas Andraschko:
Hi,
as far as i can see, the PartialViewContextImpl sets No-Cache to all AJAX
requests.
Is this required in all cases?
We have an application with nearly static data which will changed only at
night.
Our search queries are implemented via URL params and the cache-header is
set to expires at 22:00.
In one list, we must implement an filter function via AJAX and this will
not be cached.
Any idea if this could produce any other problems?
Should i overwrite this behavior for this view? How can i do it without
much effort?
Or it is better to implement this also via URL params?
Thanks and best regards,
Thomas