I am using Tomcat 6.0.20-2ubuntu2.2 on an AWS-hosted 64-bit Ubuntu 9.10
running on Java SE Runtime Environment (build 1.6.0_15-b03) and I am having
difficulty emulating getPathInfo() behaviour that works in other servlet
containers (jetty and resin)
I have a JSP file under ROOT:
<%...@page language="java" contentType="text/plain"
session="false" buffer="2kb"
%>
<path-info><%= request.getPathInfo() %></path-info>
<path-translated><%= request.getPathTranslated() %></path-translated>
<query-string><%= request.getQueryString() %></query-string>
when called with http://localhost:8080/test.jsp it reports three nulls
when called with http://localhost:8080/test.jsp?query it reports the
query-string
however when called with http://localhost:8080/test.jsp/this it fails as a
404 not found
by comparison, on a resin-4 server running the same jsp code, same os and
java version
when called with http://localhost:8080/test.jsp it reports
<path-info>/test</path-info>
<path-translated>/opt/resin-4/webapps/ROOT/test</path-translated>
<query-string>null</query-string>
and when called with http://localhost:8080/test.jsp/this?query it gives the
expected
<path-info>/test</path-info>
<path-translated>/opt/resin-4/webapps/ROOT/test</path-translated>
<query-string>query</query-string>
what could I have messed up in the installation? could tomcat6 be
encountering a conflicting jar file before its expected version? do I need
to enable some feature to get pathinfo parsing on jsp files?
--
*Have Blog, Will Travel: blog.teledyn.com*
*A Serviceable Substitute: post.teledyn.com*
