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=17310>.
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=17310
;jsessionid confuses StandardHost....can't find Context
Summary: ;jsessionid confuses StandardHost....can't find Context
Product: Tomcat 5
Version: 5.0.0
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: hoju@visi.com
Using Tomcat5 that I built from source today.
When I open a new browser and go to my context...
http://localhost:8081/xmlc/
the index.html redirects to this page:
http://localhost:8081/xmlc/ReloadTest?docClass=xmlc.demo.WelcomeHTML
All is fine so far. However, the URL's in the links of the latter page look
something like this:
http://localhost:8081/xmlc/ReloadTest;jsessionid=FF350A3154EDE9395DA1109ECAB92D82?docClass=xmlc.demo.test01HTML
When I go the latter page I get the following error in the browser....
HTTP Status 500 - No Context configured to process this request
type Status report
message No Context configured to process this request
description The server encountered an internal error (No Context configured to
process this request) that prevented it from fulfilling this request.
Apache Tomcat/5.0
The console looks like this:
30688 [Thread-5] INFO core.ContainerBase - Mapping contextPath='/xmlc' with
requestURI='/xmlc/ReloadTest' and relativeURI='/ReloadTest'
30688 [Thread-5] INFO core.ContainerBase - Trying exact match
30688 [Thread-5] INFO core.ContainerBase - Mapped to servlet 'ReloadTest' with
servlet path '/ReloadTest' and path info 'null' and update=true
51110 [Thread-5] ERROR core.StandardHost - MAPPING configuration error for
request URI
In the access log, I get this:
127.0.0.1 - - [22/Feb/2003:15:27:28 -0600] "GET
/xmlc/ReloadTest?docClass=xmlc.demo.test01HTML HTTP/1.1" 500 842
Seems like a URL parsing problem in the StandardHost where it isn't able to
figure out the context path appropriately so it doesn't know what context to
delegate the request to.
I don't have this problem at all in Tomcat-4.1.19 so it is definitely Tomcat-5
specific.
Jake
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org