Re: MMS m-notification-ind and test_ppg

On Tuesday, December 3, 2002, at 07:07 PM, Alex Judd wrote:

> Yep agreed.
>
> We can either force all carriage returns to use the CRLF standard on 
> parsing
> of the page (recommended route) or have a system/carriage return 
> character
> switch on the command line.

I would go for standard confirming

>
> There's a few other minor modifications I'd like to make to test_ppg 
> etc. so
> I'd be happy to implement the changes necessary.
>
> BTW does the content look right?

Yes, all mandatory headers were there.

Aarno

>
> Alex
>
> ----- Original Message -----
> From: "Aarno Syvänen" <[email protected]>
> To: "Alex Judd" <[email protected]>
> Cc: <[email protected]>
> Sent: Tuesday, December 03, 2002 3:41 PM
> Subject: Re: MMS m-notification-ind and test_ppg
>
>
>> This indeed causes problems, though CRLF line break is one defined by
>> MIME standard. Perhaps command line option for line break would be
>> usefull - i mean one translating input break to standard ones.
>>
>> Aarno
>>
>> On Friday, November 29, 2002, at 05:13 PM, Alex Judd wrote:
>>
>>> I was using binary as wappush returns a syntax error if I wasn't
>>> encoding
>>> the data. test_ppg seems to use windows (oa,od) carriage returns for
>>> it's
>>> joined lines, whereas my system is using xnix(oa) carriage returns.
>>> Don't
>>> know if this would cause the problem
>>>
>>> I enclosed the dumps below.
>>>
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 3c 62 61 64 6d 65 73 73
>>> <badmess
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 61 67 65 2d 72 65 73 70
>>> age-resp
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 6f 6e 73 65 20 63 6f 64   onse
>>> cod
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 65 3d 22 32 30 30 30 22
>>> e="2000"
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 20 64 65 73 63 3d 22 4e
>>> desc="N
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 6f 74 20 75 6e 64 65 72   ot
>>> under
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 73 74 6f 6f 64 20 64 75   
>>> stood
>>> du
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 65 20 74 6f 20 6d 61 6c   e to
>>> mal
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 66 6f 72 6d 65 64 20 73
>>> formed s
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 79 6e 74 61 78 22 3e 3c
>>> yntax"><
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 2f 62 61 64 6d 65 73 73
>>> /badmess
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 61 67 65 2d 72 65 73 70
>>> age-resp
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 6f 6e 73 65 3e 3c 2f 70
>>> onse></p
>>> 2002-11-29 17:11:42 [1] DEBUG:   data: 61 70 3e                  ap>
>>>
>>>> From debugging the message the total wappush is
>>>
>>> POST /wappush?username=xxxx&password=yyyy HTTP/1.1
>>> (0a,0d)Host: localhost:8080
>>> (0a,0d)Content-Type:multipart/related; boundary=asdlfkjiurwghasf;
>>> type="application/xml"
>>> (0a,0d)X-WAP-Application-Id: mms.ua
>>> (0a,0d)Content-Length: 779
>>> (0a,0d)
>>> (0a,0d)
>>> (0a,0d)--asdlfkjiurwghasf
>>> (0a,0d)Content-Type: application/xml
>>> (0a,0d)<?xml version="1.0"?>
>>> (0a)<!DOCTYPEpap PUBLIC "-//WAPFORUM//DTD PAP//EN"
>>> "http://www.wapforum.org/DTD/pap_1.0.dtd">
>>> (0a)<pap>
>>> (0a) <push-message push-id="[email protected]"
>>> progress-notes-requested="false">
>>> (0a)   <address
>>> address-value="WAPPUSH=+447753897722/[email protected]">
>>> (0a) </address>
>>> (0a)  </push-message>
>>> (0a)</pap>
>>> (0a,0d)
>>> (0a)--asdlfkjiurwghasf
>>> (0a,0d)Content-Type: application/vnd.wap.mms-message
>>> (0a,0d)Content-Type:application/vnd.wap.mms-message
>>> (0a)X-Mms-Message-Type:m-notification-ind
>>> (0a)X-Mms-Transaction-Id:125
>>> (0a)X-Mms-Version:1.0
>>> (0a)X-Mms-Message-Class:Personal
>>> (0a)X-Mms-Message-Size:4910
>>> (0a)X-Mms-Expiry:256;type=relative
>>> (0a)X-Mms-Content-Location:http://212.118.244.25/mmstest/m4.mms
>>> (0a)X-WAP-Application-Id:x-wap-application:mms.ua\
>>> (0a,0d)
>>> (0a)--asdlfkjiurwghasf--
>>>
>>>
>>
>
>