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

2003-06-20 Thread Stipe Tolj
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

[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



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

2003-06-20 Thread Vjacheslav Chekushin
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 Chekushinmailto:[EMAIL PROTECTED]
Latvian Mobile Phone Companyhttp://www.lmt.lv



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

2003-06-20 Thread Stipe Tolj
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



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

2003-06-20 Thread Stipe Tolj
Vjacheslav,

 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=/

could you please add this as a bug report to http://bugs.kannel.org/
so that it does not get forgotten?! Please.

Someone will have to pick this issue up and implement this inside the
WSP header packing/unpacking routines.

Unfortunatly I'm unable now.

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



[RFC] cookie support per detault in wapbox?!

2003-06-19 Thread Stipe Tolj
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?

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