derkoe,
I think this is the simplest way:
public static void
contributePageRenderRequestHandler(OrderedConfiguration
configuration)
{
configuration.addInstance("NoCacheHeaderRequestFilter",
NoCacheHeaderRequestFilter.class);
}
public static void
contributeAjaxCompo
For our project, every tapestry page includes dynamic content, therefore
we do not want any cache used on the client.
Thanks for the tip.
On 25/02/2012 8:22 AM, derkoe wrote:
Paul Stanton-4 wrote
Hi All,
Hi!
Paul Stanton-4 wrote
In a t5.1 app, I thought it was worth checking every reques
Paul Stanton-4 wrote
>
> Hi All,
>
Hi!
Paul Stanton-4 wrote
>
> In a t5.1 app, I thought it was worth checking every request path and
> setting the 'no-cache' response headers for all page/ajax requests.
>
> I'm not sure if this is still needed, but my required behaviour is that
> all pag
