Hi!,
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
-To: mailing list [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Thu, 22 Feb 2001 17:37:35 +0100
Subject: RE: Tomcat - Sessions and WAP Browsers
Priority: Normal
X-mailer: Phoenix Mail 0.92.08 Standard Edition
MIME-Version: 1.0
Content-type: multipart/mixed; boundary=-Phoenix
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 as
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 that
is secured,
