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=10629>. 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=10629 include directive fails when referencing Parent Path within a WAR Summary: include directive fails when referencing Parent Path within a WAR Product: Tomcat 4 Version: 4.1.7 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] using the include directive fails when referencing the Parent path when the Context is set directly to the WAR file, yet succeeds when accessing the unpacked WAR directories. This Context fails: <Context path="/ServerTest" docBase="ServerTest.war" debug="0" privileged="true" /> but expanding the war and setting this context succeeds <Context path="/ServerTest" docBase="ServerTest" debug="0" privileged="true" /> the test files were setup as such: (the WAR will be attached) /inc.htm /testdir/DotDotInclude.jsp where DotDotInclude.jsp has a tag <%@ include file="../inc.htm"%> Hacking at the source code for jasper2 revealed that when the call was made to JSPCompilationContext.getResourceAsStream(String res) res = "/testdir/../inc.htm" The returned java.io.InputStream was null if the WAR was the Context docBase, and not null if referencing the directory. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
