Very Computer

I have a problem where the input stream containing POST information is
not
getting through from WAP phones to my application - can anyone help
with the following?

The configuration we have is UP.Link 4.2.1.2 WAP gateway and IBM /
Apache HTTP
server 1.3.6.3, running on Solaris 5.7.

If I use a Mitsubishi Trium phone, POST requests work fine. If I use a
Nokia phone (or the Nokia phone simulator) the POST request gets
through,
but none of the POST data.

The problem appears to be how the HTTP Server handles the POST request.
Using Snoop on Solaris, in both situations I see the HTTP POST request
and
input data coming through. However, the HTTP Server logs tell a
different
story: in the cases where the POST works, I see a normal POST request in
the logs. In the cases where it does not work, I see two
requests: first, the POST request is logged as before. Immediately
following that is a second request containing the POST input data,
i.e. the HTTP Server treats the POST input stream as a separate request,
and throws an error because it obviously doesn't recognise the POST
input
data is a valid HTTP method.

Has anyone seen anything similar to this, or can suggest what might be
causing the HTTP Server to handle the POST request in this way?

I did find one (old) post on the Apache bug database that looked similar
(but not identical) that recommended checking the request headers sent
by the client. In my case, some of these headers are added by the phone,
and some by the gateway. In particular I'm wondering if this is anything
to do with the "Accept-Charset" header?

If anyone asks I can post contents of
the Snoop or HTTP server logs.

Thanks in advance for any comments,

Rick

Sent via Deja.com
http://www.deja.com/

POST request that worked fine:

(Note - hostnames, addresses are fictitious, the rest is real)

POST /wtp/ht_tp:/111.111.111.111/WMLTestServlet HTTP/1.1
x-up-uplink: wap.gateway.server
x-up-fax-limit: 100000
x-up-subno: 964186734-26138_wap.gateway.server
x-up-fax-accepts: text/plain, application/postscript,
application/msword, application/rtf, application/pdf
host: 111.111.111.111:80
Accept-Language: en
User-Agent: Mitsu/1.1.A UP.Link/4.2.1.2
x-up-devcap-max-pdu: 8192
x-up-devcap-charset: utf-8, iso-8859-1
x-up-WTLS-info: off
Connection: Keep-Alive
Content-Type: application/x-www-form-urlencoded
x-up-fax-encodings: 7bit, 8bit, base64, quoted-printable
Accept: application/vnd.wap.wmlc, image/gif, image/vnd.wap.wbmp,
application/vnd.wap.wmlscriptc, images/x-wap.wbmp, images/vnd.wap.wbmp,
image/bmp,image/vnd.wap.wbmp,text/x-wap.wml,text/vnd.wap.wml,text/x-
hdml,text/html,text/vnd.wap.wmlscript
x-up-devcap-post-charset: US-ASCII
Content-Length: 12
Accept-Charset: utf-8, iso-8859-1, UTF-8, *

TEST=TRIUM2Q

POST request that did not work

POST /wtp/ht_tp://111.111.111.111/WMLTestServlet HTTP/1.1
x-up-uplink: wap.gateway.server
host: 111.111.111.111:80
x-up-devcap-max-pdu: 8192
User-Agent: Nokia-WAP-Toolkit/2.0 UP.Link/4.2.1.2
x-up-devcap-charset: utf-8
x-up-WTLS-info: off
Connection: Keep-Alive
Content-Type: application/x-www-form-urlencoded
Accept: application/vnd.wap.wmlc, application/vnd.wap.wmlscriptc,
text/x-vCard, text/x-vCard, text/x-vcal, text/x-vCalendar, text/x-
vCalendar, image/vnd.wap.wbmp, application/vnd.wap.wbxml, image/gif,
image/jpeg, image/bmp,image/vnd.wap.wbmp,text/x-
wap.wml,text/vnd.wap.wml,text/x-hdml,text/html,text/vnd.wap.wmlscript
x-up-devcap-post-charset: US-ASCII
Content-Length: 29
Content-Length: 29
Accept-Charset: utf-8, UTF-8, *

TEST=postnokiadirect

HTTP Server log for failed POST request:

222.222.222.222 - - [14/Dec/2000:16:13:53
+0000] "POST /wtp/ht_tp://111.111.111.111/WMLTestServlet HTTP/1.1" 200
194
222.222.222.222 - - [14/Dec/2000:16:13:53 +0000] "TEST=postnokiadirect"
501 -

Sent via Deja.com
http://www.deja.com/