tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: Tomcat - Sessions and WAP Browsers
Date Thu, 22 Feb 2001 16:37:35 GMT

Actually, WAP protocol does not support cookies (at least the version I 
worked on).

You have to deal with URL Rewriting, in order to include the session ID 
into the requested URL. Once there, tomcat automatically reads the session 
ID from the URL instead of using the cookie. This is the same as when 
programming standard HTML pages with browsers without cookies support.

Take a look to the 'HttpServletResponse' class and the method 'encodeURL'. 
This will made the task of including the Session ID in the URL if needed.

Hope this helps.




> The real problem I am running into is that most WAP browsers don't support
> cookies and thus the storing of session data in the cookie. I use Tomcat 
> my servlet engine, and I have a secured part of my site. 
> How Tomcat works in a web environment is this. When you request a page 
> is secured, tomcat places the session variable
> 'tomcat.auth.originalLocation' into the session. This variable holds onto
> the requested URL. After placing the variable into the session, it 
> you to your specified login page i.e. '/secure/login.jsp'. Upon successful
> login/authentication it will forward you to the page referenced in the
> 'tomcat.auth.originalLocation' session variable, along with placing a few
> more variables in the session.
> This becomes a problem in the WAP browser environment because none of the
> WAP browsers support cookies, thus cannot get access to the session 
> 'tomcat.auth.originalLocation'.
> Hope this makes more sense?
> Thanks for your thoughts,
> Bob


  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message