If your problem occurs in multiple pages I recommend put the cache
configuration in your AppModule.
public RequestFilter cacheFilter() {
return new RequestFilter() {
public boolean service(Request request, Response
response, RequestHandler handler) throws IOException {
response.setHeader("Cache-Control","no-cache");
//HTTP 1.1
response.setHeader("Pragma","no-cache"); //HTTP
1.0
response.setDateHeader ("Expires", 0); //prevents
caching
response.setHeader("Cache-Control","no-store");
//HTTP 1.1
return handler.service(request, response);
}
};
}
2011/2/21 Martin Strand <do.not.eat.yellow.s...@gmail.com>
> If you want to use the exact same URL to serve different content, you'll
> need to make sure the response is never cached by the client.
> Add appropriate HTTP headers to the response:
>
> @Inject
> private Response response;
>
> void onActivate(...)
> {
> response.setHeader("Cache-Control", "no-cache");
> response.setDateHeader("Expires", 0);
>
> }
>
>
>
>
> On Mon, 21 Feb 2011 05:11:43 +0100, sunmoor007 <sunmoo...@gmail.com>
> wrote:
>
>
>> Hi Josh
>>
>> Thanks for your response. You're right. We dont have the search parameter
>> in
>> the URL but wondering how does it work in a scenario where there no proxy
>> server. I have seen an option disableCaching. If i enable that, will it
>> work.
>>
>> Considering the option you mentioned, am guessing if we can add some
>> dynamic
>> parameter in url which changes for each request which should resolve the
>> problem.
>>
>> I will anyway check the proxy logs.
>>
>> Thanks
>> Sundar
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
--
Pablo Henrique dos Reis
