Bug 5481 - Standard EA3 import does not work when using Opera browser
Summary: Standard EA3 import does not work when using Opera browser
Alias: None
Product: Taglibs
Classification: Unclassified
Component: Standard Taglib (show other bugs)
Version: unspecified
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2001-12-18 04:12 UTC by Sam Cooper
Modified: 2005-03-20 17:06 UTC (History)
0 users

Request response debug output from Tomcat 4.0.1 (36.15 KB, text/plain)
2001-12-18 04:14 UTC, Sam Cooper
Example web archive which shows problem (5.55 KB, application/octet-stream)
2001-12-18 04:15 UTC, Sam Cooper
Java http request code that shows the same problem. (1.66 KB, application/octet-stream)
2001-12-18 06:46 UTC, Sam Cooper

Note You need to log in before you can comment on or make changes to this bug.
Description Sam Cooper 2001-12-18 04:12:50 UTC
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.

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 

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.

Comment 1 Sam Cooper 2001-12-18 04:14:09 UTC
Created attachment 913 [details]
Request response debug output from Tomcat 4.0.1
Comment 2 Sam Cooper 2001-12-18 04:15:05 UTC
Created attachment 914 [details]
Example web archive which shows problem
Comment 3 Sam Cooper 2001-12-18 06:45:16 UTC
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!
Comment 4 Sam Cooper 2001-12-18 06:46:11 UTC
Created attachment 915 [details]
Java http request code that shows the same problem.
Comment 5 Shawn Bayern 2001-12-18 07:48:42 UTC

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

Comment 6 Sam Cooper 2001-12-18 08:47:41 UTC
Thought this might be the case, I'll try and open it on that list!