Vjacheslav Chekushin wrote: > > Hi, list. > > I've encode Set-Cookie header as specified in WSP (encoding-version 1.3): > > c1 - Set-Cookie header > 0e - value-length > 9f - version (1) > 74 t > 65 e > 73 s > 74 t > 00 > 73 s > 73 s > 73 s > 73 s > 73 s > 73 s > 73 s > 00 > > (From WSP: > Set-Cookie-value = Value-length Cookie-version Cookie-name Cookie-val *Parameter > Cookie-version = Version-value > Cookie-name = Text-string > Cookie-val = Text-string) > > But seems phone does not accept it. (At least it does not send Cookie header > back to server) > > I can't find out where I am wrong. > > Test phone is SonyEricsson t68i and it accepts encoding version 1.3
did you ask the Ericsson developer's zone (where some of the staff is answering) if the phone is able to do the operation? AFAIK, even while phones indicate specific encoding versions, that *does not* mean they have all the sets implemented. Is the set-cookie feature in encoding version 1.3 optional or mandatory according to the WSP specs and unit conformance documents?! Stipe mailto:[EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG M�nsterstr. 248 40470 D�sseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ ------------------------------------------------------------------- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -----END PGP PUBLIC KEY BLOCK-----
