08-25-2010 06:55 PM
When I make the following request
uest HTTP/1.1 Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Content-Type: multipart/related; boundary=mPsbVQo0a68eIL3OAxnm; type=application/xml Authorization: Basic [removed] Host: pushapi.eval.blackberry.com Content-Length: 607 Expect: 100-continue Connection: Keep-Alive --mPsbVQo0a68eIL3OAxnm Content-Type: application/xml; charset=UTF-8 <?xml version="1.0"?> <!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 2.1//EN" "http://www.openmobilealliance.org/tech/DTD/pap_2.1 .dtd"> <pap> <push-message push-id="12345" deliver-before-timestamp="2010-08-26T06:59:30Z" source-reference="app id"> <address address-value="WAPPUSH=12345678%3A12345/TYPE=USER@ rim.com" /> <quality-of-service delivery-method="confirmed"/> </push-message> </pap> --mPsbVQo0a68eIL3OAxnm Content-Type: text/plain testing --mPsbVQo0a68eIL3OAxnm--
I get this response...
HTTP/1.1 200 OK Date: Wed, 25 Aug 2010 22:37:00 GMT Server: Apache Set-Cookie: JSESSIONID=02343458D4926A74D45678ABF; Path=/mss Pragma: no-cache Cache-Control: no-cache Content-Length: 293 Keep-Alive: timeout=15, max=100 Connection: Keep-Alive Content-Type: application/xml <?xml version="1.0"?> <!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 2.1//EN" "http://www.openmobilealliance.org/tech/DTD/pap_2.1
.dtd"><pap><badmessage-response code="2000" desc="Invalid or missing attribute address-value" bad-message-fragment="Invalid or missing attribute address-value"/></pap>
I'm not sure what is wrong with the address-value since it is exactly what is documented in http://docs.blackberry.com/en/developers/deliverab
<address address-value="12345678" />
I get the <response-result code="1001" desc="The request has been accepted for processing."></response-result>, but it doesn't seem to reach the device's listening port. Because of this, I tried adding the "WAPPUSH=12345678%3A12345/TYPE=USER@rim.com" format to see if putting the port in the address would help. Does anyone know what the problem with either my address-value attribute that would cause the first error, or what I'm missing in the entire request that is causing the port to not be reached.