> 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.
You should consider putting your search terms in the url either as a path parameter or a query parameter so that you can take advantage of caching. Unless it's user specific data which you don't want exposed, then you want to tell the proxy not to cache using the appropriate http headers. Either way it's worthwhile to learn about the built in HTTP caching options so that you can be sure you're using it correctly. Josh On Sun, Feb 20, 2011 at 8:11 PM, 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 > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Tapestry-5-cache-issue-when-accessed-via-proxy-tp3388994p3393672.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
