I'm not sure what is causing this problem, whether it is the Standard taglib implementation or a bug in Tomcat 4.0.1. Basically, I am trying to use the new Standard taglib to perform XSL transformations. What my pages do is use the core:import tag to load an XSL from a local resource file and pass it to a xml:transform. This works fine under IE 5.5 and Netscape but under Opera 5 and 6 I get very strange behaviour. The first time I visit the page it works fine, but if I visit the page from another page the import does not happen. The attribute in the page context has been created but it is empty. I have created a small web archive to demostrate this and have attached it. You will need to put the EA3 jars in the WEB-INF lib directory before it works. To get this strange behaviour you have to vist the two pages using the links provided. After a couple of visits the imported text on the first page does not get displayed unless you do a refresh on that page. I have also included a request/response dump from catalina which shows this procedure first done with IE and then using Opera. The only major difference that I can see is the header-referer field. Once again, this works fine in IE and Netscape. Thanks. Sam.
Created attachment 913 [details] Request response debug output from Tomcat 4.0.1
Created attachment 914 [details] Example web archive which shows problem
After further testing it seems it has nothing to do with the referer field but to do with the if- modified-since field, something that Opera always provides once it has seen a page but IE does not seem to. I have created a little Java program to do this, you will have to edit it to provide the correct URL!
Created attachment 915 [details] Java http request code that shows the same problem.
Sam, Thanks for the detailed information. However, I don't see how this can be related to JSTL, given that the Standard Taglib's behavior isn't modified or affected in any way by HTTP headers. The behavior sounds like a container- related issue; whether it's a bug or not is probably best a question for the container maintainers. Please feel free to re-open this bug if you discover any new information that appears to implicate the tag handlers (or other code) associated with JSTL. Shawn
Thought this might be the case, I'll try and open it on that list!