DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9745>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9745 extern cache mgt bug for conditionally dynamic pages Summary: extern cache mgt bug for conditionally dynamic pages Product: Tomcat 4 Version: 4.0.4 Beta 3 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Servlet & JSP API AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] We have seen an interesting bug here having to do with external cache management in conditionally static pages. The bug scenario, seen in a jsp, is as follows: 1) Have conditional forward to a non-xsl, static file (html in this case). 2) Otherwise have xsl transform. 3) User goes through some scenario that goes first by xsl, then by non-xsl. 4) Fetch the jsp by GET. In this case, the browser cache will be primed with the result of the XSL generation. Then, when it goes through the static page case, it will observe that the page is unchanged and send a 304 Unmodified reply to the browser. The browser, in turn, will use the version of the file that it last saw. Oops! This bug has been verified to exist under 4.0.3 and 4.0.4b. Code that reproduces this scenario is included with this message in a .tar.gz file intended to be extracted in a webapps directory as an application directory named 'bugreport. You can run the code by going to: http://localhost/bugreport/ When you hit the button labeled 'Do The Bug,' you will be taken through a jsp case that sends it to an alternate file, unseen.html, but you will never see that file because you will stick with the test.xsl that was first displayed, that contains that button. Oops! There are some embedded debugging printlns that show which way the jsp decision branch is going, and why. Thank you for looking at this report, and indeed for all your work on Tomcat, which make projects like ours possible. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
