WAP cookie support depends on the gateway which is controlled by the
service provider. I have experienced one provider in the U.S. which
supported cookies. It was so long ago now that I've forgotten which
provider that was.
The app I wrote started out each session using both a cookie and a
search string and if the cookie came back, I dropped the search string.
It's especially convenient when cookies work because it's such a pain to
re-enter passwords from a telephone keypad.
Rafal Krzewski wrote:
>
> Jon Stevens wrote:
> > > Tomcat will probably solve your JServSessionId problems.
> >
> > Not necessarily. The problem is that for some reason, the WAP client doesn't
> > seem to support cookies or redirects or you are using sessions improperly or
> > all of the above so JServ (and also Tomcat) won't encode things using a
> > cookie.
>
> AFAIK WAP enabled phones DO NOT support cookies. You need to use 'URL
> encoding'
> to maintain a session.
>
> Rafal
>
> --
> Rafal Krzewski
> Senior Internet Developer
> mailto:[EMAIL PROTECTED]
> +48 22 8534830 http://e-point.pl
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
