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=/
Stipe Tolj wrote:
Stipe Tolj wrote:
Hi list,
I'd like to throw the --enable-cookie directive from configure and make cookie support for wapbox now a permanent default feature.
Any objections for doing this?
no objections?! Votes please.
Stipe
-- Vjacheslav Chekushin mailto:[EMAIL PROTECTED] Latvian Mobile Phone Company http://www.lmt.lv
