Re: [RFC] cookie support per detault in wapbox?!

Vjacheslav Chekushin wrote:
> 
> Hi, Stipe.
> There are 2 issues.
> Current cookie implementation cache this cookie in session machine.
> So it works only for connection-oriented mode and only for
> current session. From other side,
> WAP user can't manage own cookies with this approach.
> And by cookie's RFC (RFC 2109) user agent must be able "to completely disable
> the sending and saving of cookies" (7.1)
> 
> So I recommend to support cookies by implementing normal
> WSP<->HTTP cookie header encoding, couse almost all modern WAP phones
> can deal with cookies by itself.
> 
> Current implementation doesn't know how to encode Cookie's headers:
> 
> 2003-06-20 14:20:56 [1] ERROR: WSP: Do not know how to encode header type 65
> 2003-06-20 14:20:56 [1] WARNING: Skipping header: Set-Cookie:
> JSESSIONID=bhFsO7t57CM7; Path=/

ahh, ok.

Can we determine via the WSP headers send by the device if it's
capable to handle cookies on it's own?

If yes, we can have them store the cookies and for older phones
leaving them in the session cache scope of Kannel?!

Stipe

[email protected]
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [email protected]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are