Hi David, > 2003-07-18 11:49:20 [10] DEBUG: HTTP: Status line: <HTTP/1.1 301 Moved > Permanently>
so wap.sonyericsson.com does reply with a HTTP 301, hence Kannel should follow the Location header. > 6e 74 65 6e 74 chunked..Content > 2003-07-18 11:49:20 [10] DEBUG: data: 2d 54 79 70 65 3a 20 74 65 78 74 > 2f 68 74 6d 6c -Type: text/html and the response body is text/html encoded, hence > 2003-07-18 11:49:20 [8] WARNING: WSP: Content type <text/html> not > supported by client, deleting body. > 2003-07-18 11:49:20 [8] WARNING: WSP: content-type text/plain not supported Kannel claims that the content-type is not accepted by the client and replies with a non-displayable WSP message. This effect has nothing to do with cookies, btw. I just wonder why Kannel's HTTP module did not follow the HTTP Location?! Anyone having an idea if the WAP specific HTTP calls are reglemented for following the HTTP Location header?! 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
