https://bz.apache.org/bugzilla/show_bug.cgi?id=62971
fuminz...@crd.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|DUPLICATE |---
Status|RESOLVED |REOPENED
--- Comment #2 from fuminz...@crd.com ---
The fix to bug 49464 potentially missed a scenario in its consideration, and
may have introduced a "new" bug. However, we have not been able to create an
isolated test scenario to demonstrate such yet.
In comments to bug 49464, it listed 3 scenarios considered: "
There are three scenarios to consider:
a) directly returning a file
b) including a file into an output stream
c) including a file into a writer".
However, a fourth scenario <c:import...> for standard tag library core appears
to be impacted.
To my understanding, if a jsp contains a:
<c:import var="xslt" url="/sample.xsl"/>
it is supposed to populate the content from that file "sample.xsl" into the
"variable" "xslt", for later code to use.
The issue behavior that we (in certain conditions) observed, is that the
"variable" "xslt" would become empty, yet the jsp or the result html would
receive the content of "sample.xsl" as part of its own content, making it
behaving as if it is a "include" tag instead of an import tag.
We have not identified the exact conditions that would trigger such behavior
yet - thus no isolated test case created to demonstrate such yet. But since
the issue behavior looks to match the comments of the bug/fix for 49464, I am
adding this comment to start the communication. - We will update when/if we
have more specific info.
We are using tomcat 9.0.26
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
