Posted By:
Gerhard_Wich
Posted On:
Sunday, July 14, 2002 12:25 AM
I try to set up a dipatcher page and use URL rewriting for session id handling. The code looks something like that: String whereTo = response.encodeURL("password_entry.jsp"); . . if ( ! userAccessGranted ) pageContext.forward(whereTo); When I run this on a tomcat 4 server, I get the error: --------------------------- Apache Tomcat/4.0.2 - HTTP Status 404 - description The requested resource (/password_entry.jsp;jsessionid=79DDF0D5076B495A75C0BFB9EF93157E/) is not available. --------------------------- (by the way, the same happens if I put the rewritten URL into a action.) The addre
More>>
I try to set up a dipatcher page and use URL rewriting
for session id handling. The code looks something like that:
String whereTo = response.encodeURL("password_entry.jsp");
.
.
if ( ! userAccessGranted ) pageContext.forward(whereTo);
When I run this on a tomcat 4 server, I get the error:
---------------------------
Apache Tomcat/4.0.2 - HTTP Status 404 -
description The requested resource
(/password_entry.jsp;jsessionid=79DDF0D5076B495A75C0BFB9EF93157E/) is not available.
---------------------------
(by the way, the same happens if I put the rewritten URL into a
action.)
The addressed page, of course, exists. Writing instead:
if ( ! userAccessGranted ) pageContext.forward("password_entry.jsp");
works fine, but then I loose the session id.
How do I get around this? Does tomcat have a problem
with forwarding in combination with URL-rewriting?
Best Regards, Gerhard.
