You haven't given us a lot to work with so I'll speculate that you're app doesn't keep the search parameters in the URL after the redirect-after-post so the browser is always fetching the same url.
Have you tried looking at the proxy logs to see what its doing? On Feb 16, 2011 11:17 PM, "sunmoor007" <sunmoo...@gmail.com> wrote: > > Hello All > > We have developed a web application using Tapestry 5. We are facing a > caching issue when we try to access the application via a proxy. When we > access the application directly i.e without going via a proxy server, > everything is working fine. > > when we access via proxy we are seeing this problem. A simple example is a > search screen. We first seach using a criteria and appilcation returned a > result. Later when we search using a different criteria we are seeing the > old entries in page. When we do a refresh or CTRL f5 manually, we are seeing > the updated values. > > Is there any solution or workaround to this problem from Tapestry 5 point of > view. Would really appreciate if you can help on this. > > thanks > Sundar > -- > View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-5-cache-issue-when-accessed-via-proxy-tp3388994p3388994.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 >
