Hi Martin We did try setting the cache headers but it didnt work. Moreover this application works fine when accessed directly. The problem comes only when the application is accessed via proxy server. Thats the reason i have suspected the URL.
We did a workaround at proxy server setting level so that all requests with a particular path wont be cached by proxy server. This did work but we are looking forward for a fix from application point of view instead of relying the proxy server setting workaround. Thanks Sundar -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-5-cache-issue-when-accessed-via-proxy-tp3388994p4191583.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
