I meant one with content, and no capabilities.
(Of course crash with capabilities is a bug.)

Aarno

On Friday, July 11, 2003, at 05:36 PM, Henrik Kniberg wrote:

OK, here's a version with push content. Wapbox manages to get a lot further
now (by the way wapbox is very picky about, Content-Length, although it is
never included in any examples), but then it dies with a segmentation fault
every time.


Has anyone actually managed to submit a wap push message of any sort?


=== WAP BOX OUTPUT =================


2003-07-11 17:28:01 [11] DEBUG: HTTP: Creating HTTPClient for `192.168.0.16'.

2003-07-11 17:28:01 [14] INFO: PPG: Accept request </wappush> from
<192.168.0.16>
2003-07-11 17:28:01 [14] DEBUG: PPG: http_read_thread: pap multipart accepted


2003-07-11 17:28:01 [14] INFO: client address was <+46704925284>, accepted
2003-07-11 17:28:01 [14] DEBUG: PAP COMPILER: doing semantic analysis for
address type a phone number
2003-07-11 17:28:01 [14] DEBUG: PAP COMPILER: network orbearer missing,
reverting to GSM+SMS
2003-07-11 17:28:01 [14] INFO: reverting to default bearer and network
2003-07-11 17:28:01 [14] DEBUG: PPG: http_read_thread: pap control entity
compiled ok
Segmentation fault


==== HTTP REQUEST THAT KILLED IT ====================

POST /wappush HTTP/1.1
host: www.kniberg.com:13003
Content-Type: multipart/related; boundary=asdlfkjiurwghasf;
type="application/xml"
Content-Length: 1160

--asdlfkjiurwghasf
Content-Type: application/xml

<?xml version="1.0"?>
<!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 1.0//EN"
"http://www.wapforum.org/DTD/pap_1.0.dtd";>
<pap>
<push-message push-id="[EMAIL PROTECTED]">
<address address-value="WAPPUSH=+46704925284/[EMAIL PROTECTED]"/>


  </push-message>
</pap>

--asdlfkjiurwghasf
Content-Type: text/vnd.wap.wml
<?xml version="1.0"?>
<!DOCTYPE WML PUBLIC "-//WAPFORUM//DTD WML 1.1//EN"
"http://www.wapforum.org/DTD/wml_1.1.xml";>
<wml>
  <card>
    <p>Hello World!</p>
  </card>
</wml>

--asdlfkjiurwghasf
Content-Type: application/xml

<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
xmlns:prf="http://www.wapforum.org/UAPROF/ccppschema1.0#";>
  <rdf:Description>
    <prf:WapVersion>1.1</prf:WapVersion>
    <prf:WmlDeckSize>1400 octets</prf:WmlDeckSize>
    <prf:WapDeviceClass>A </prf:WapDeviceClass>
    <prf:WapPushMsgSize>1400 octets</prf:WapPushMsgSize>
    <prf:WmlVersion>
      <rdf:Bag>
        <rdf:li>1.1</rdf:li>
      </rdf:Bag>
    </prf:WmlVersion>
  </rdf:Description>
</rdf:RDF>

--asdlfkjiurwghasf--
=====================================================

--
Henrik Kniberg
Epicent AB
[EMAIL PROTECTED]
+46 (0)704925284

Aarno Syv�nen wrote:

Push content seems to be missing. Or if you have, please send the
whole multipart.

Aarno

On Tuesday, July 8, 2003, at 08:07 PM, Henrik Kniberg wrote:

Hi,

This post is related to Magnus Adlers's.

I'd greatly appreciate if someone could post an example of a simple but
complete WAP Push request (with http headers and all) that wapbox
accepts. There are examples in the docs, but they only show the pap
xml, not the complete http request.


I've tried about 20 variants of the following HTTP message, adding a
new
line here or there, removing headers, etc, based on various
specifications and examples that I've found. Each time I get a slightly
different error message. Here is the version that seems to get me
furthest:


=====================================
POST /wappush HTTP/1.1
host: www.kniberg.com:13003
Content-Type: multipart/related; boundary=EndOfOneEntity;
type="application/xml"
Content-Length: 372

--EndOfOneEntity
Content-Type: "application/xml"
<?xml version="1.0"?>
<!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP//EN"
          "http://www.wapforum.org/DTD/pap_1.0.dtd";>
<pap>
  <push-message push-id="[EMAIL PROTECTED]">
    <address
address-value="WAPPUSH=+358408676001/[EMAIL PROTECTED]">
    </address>
  </push-message>
</pap>
--EndOfOneEntity
=====================================

In response to this the wap box says:

2003-07-08 19:35:01 [11] DEBUG: HTTP: Creating HTTPClient for
`192.168.0.16'.
2003-07-08 19:35:01 [14] INFO: PPG: Accept request </wappush> from
<192.168.0.16>
2003-07-08 19:35:01 [14] WARNING: erroneous control entity
2003-07-08 19:35:01 [14] DEBUG: PPG: send_bad_message_response: telling
pi
2003-07-08 19:35:01 [14] DEBUG: HTTP: Resetting HTTPClient for
`192.168.0.16'.
2003-07-08 19:35:01 [14] WARNING: PPG: unable to parse mime content,
the
request unacceptable


I'm running Kannel 1.3.1 on Redhat (7.3 I think).

Cheers,

/Henrik







Reply via email to