POST requests missing POST input stream

POST requests missing POST input stream

Post by robi.. » Sat, 16 Dec 2000 19:18:52


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

The configuration we have is UP.Link WAP gateway and IBM /
Apache HTTP
server, 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
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
input data coming through. However, the HTTP Server logs tell a
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
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,


Sent via


POST requests missing POST input stream

Post by robi.. » Sat, 16 Dec 2000 19:27:26

Details from HTTP server and Snoop logs:

POST request that worked fine:

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

POST /wtp/ht_tp:/ 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
Accept-Language: en
User-Agent: Mitsu/1.1.A UP.Link/
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,
x-up-devcap-post-charset: US-ASCII
Content-Length: 12
Accept-Charset: utf-8, iso-8859-1, UTF-8, *


POST request that did not work

POST /wtp/ht_tp:// HTTP/1.1
x-up-uplink: wap.gateway.server
x-up-devcap-max-pdu: 8192
User-Agent: Nokia-WAP-Toolkit/2.0 UP.Link/
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-
x-up-devcap-post-charset: US-ASCII
Content-Length: 29
Content-Length: 29
Accept-Charset: utf-8, UTF-8, *


HTTP Server log for failed POST request: - - [14/Dec/2000:16:13:53
+0000] "POST /wtp/ht_tp:// HTTP/1.1" 200
194 - - [14/Dec/2000:16:13:53 +0000] "TEST=postnokiadirect"
501 -

Sent via


1. my PICO posts not posting...


I have had problems using pico as my default editor. What is the proper
syntax for setting up .profile and .kshrc to have pico be my default
editor (when posting to usenet)? I am writing this using VI and have
no problems posting with VI, but when I post with pico all I get is
my .sig file and nothing else. I am not a big fan of VI but is is the
default. I'll even settle for emacs if I can figure out how to get
that to be the default.

Cheers,         --Ken--
(*)(-)(*)(+)(*)(-)(*)(+)(*) from the computer of (*)(-)(*)(+)(*)(-)(*)(+)(*)

2. root-login from console and vt only


4. CABLE, DHCP and intermittent network

5. Wrong posting: ignore the previous post aboout vmsdate.

6. VFS: Mounted (root filesystem) FREEZE


8. Automate mail retrieval with cron and sendmail

9. Third-party (ecommerce) site: checking POST parameters BEFORE passing to it, OR redirecting with POST

10. Form posting problem and post data issue

11. Error on posting news, but article gets posted...

12. posting multiple posts via telnet

13. A non cross-posted post