Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce
Post Number: 4473
Registered: 10-2002
| | Posted on Wednesday, May 04, 2005 - 10:45 pm: | |
Hi Mindaugas,
I don't dispute that there is a problem. And it may very well be a chunking related problem.
However, the request that we are receiving from the K500 is not chunked.
I suspect the problem is with the proxy server ("tinyproxy") ...
I hate to pass the blame, but in this particular case, here is what we are receiving (via the proxy):
16:23:53:620 [13] ThreadProcessConnection: Packet Length is 490 bytes
16:23:53:651 [13] ThreadProcessConnection: 50 4F 53 54 20 2F 20 48 54 54 50 2F 31 2E 30 0D POST / HTTP/1.0
16:23:53:651 [13] ThreadProcessConnection: 0A 48 6F 73 74 3A 20 6D 6D 73 63 0D 0A 43 6F 6E Host: mmsc Con
16:23:53:651 [13] ThreadProcessConnection: 6E 65 63 74 69 6F 6E 3A 20 63 6C 6F 73 65 0D 0A nection: close
16:23:53:651 [13] ThreadProcessConnection: 56 69 61 3A 20 31 2E 31 20 74 69 6E 79 70 72 6F Via: 1.1 tinypro
16:23:53:682 [13] ThreadProcessConnection: 78 79 20 28 74 69 6E 79 70 72 6F 78 79 2F 31 2E xy (tinyproxy/1.
16:23:53:714 [13] ThreadProcessConnection: 36 2E 33 29 0D 0A 41 63 63 65 70 74 3A 20 61 70 6.3) Accept: ap
16:23:53:714 [13] ThreadProcessConnection: 70 6C 69 63 61 74 69 6F 6E 2F 76 6E 64 2E 77 61 plication/vnd.wa
16:23:53:714 [13] ThreadProcessConnection: 70 2E 6D 6D 73 2D 6D 65 73 73 61 67 65 2C 20 2A p.mms-message, *
16:23:53:714 [13] ThreadProcessConnection: 2F 2A 0D 0A 43 6F 6E 74 65 6E 74 2D 54 79 70 65 /* Content-Type
16:23:53:714 [13] ThreadProcessConnection: 3A 20 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E : application/vn
16:23:53:745 [13] ThreadProcessConnection: 64 2E 77 61 70 2E 6D 6D 73 2D 6D 65 73 73 61 67 d.wap.mms-messag
16:23:53:776 [13] ThreadProcessConnection: 65 0D 0A 43 61 63 68 65 2D 43 6F 6E 74 72 6F 6C e Cache-Control
16:23:53:776 [13] ThreadProcessConnection: 3A 20 6E 6F 2D 63 61 63 68 65 0D 0A 55 73 65 72 : no-cache User
16:23:53:776 [13] ThreadProcessConnection: 2D 41 67 65 6E 74 3A 20 53 6F 6E 79 45 72 69 63 -Agent: SonyEric
16:23:53:776 [13] ThreadProcessConnection: 73 73 6F 6E 4B 35 30 30 69 2F 52 32 41 41 20 53 ssonK500i/R2AA S
16:23:53:807 [13] ThreadProcessConnection: 45 4D 43 2D 42 72 6F 77 73 65 72 2F 34 2E 30 2E EMC-Browser/4.0.
16:23:53:839 [13] ThreadProcessConnection: 32 20 50 72 6F 66 69 6C 65 2F 4D 49 44 50 2D 32 2 Profile/MIDP-2
16:23:53:839 [13] ThreadProcessConnection: 2E 30 20 43 6F 6E 66 69 67 75 72 61 74 69 6F 6E .0 Configuration
16:23:53:839 [13] ThreadProcessConnection: 2F 43 4C 44 43 2D 31 2E 31 0D 0A 41 63 63 65 70 /CLDC-1.1 Accep
16:23:53:839 [13] ThreadProcessConnection: 74 2D 43 68 61 72 73 65 74 3A 20 75 74 66 2D 38 t-Charset: utf-8
16:23:53:839 [13] ThreadProcessConnection: 2C 20 75 74 66 2D 31 36 2C 20 69 73 6F 2D 38 38 , utf-16, iso-88
16:23:53:870 [13] ThreadProcessConnection: 35 39 2D 31 2C 20 69 73 6F 2D 31 30 36 34 36 2D 59-1, iso-10646-
16:23:54:042 [13] ThreadProcessConnection: 75 63 73 2D 32 0D 0A 58 2D 57 61 70 2D 50 72 6F ucs-2 X-Wap-Pro
16:23:54:073 [13] ThreadProcessConnection: 66 69 6C 65 3A 20 68 74 74 70 3A 2F 2F 77 61 70 file: http://wap
16:23:54:073 [13] ThreadProcessConnection: 2E 73 6F 6E 79 65 72 69 63 73 73 6F 6E 2E 63 6F .sonyericsson.co
16:23:54:073 [13] ThreadProcessConnection: 6D 2F 55 41 70 72 6F 66 2F 4B 35 30 30 69 52 32 m/UAprof/K500iR2
16:23:54:073 [13] ThreadProcessConnection: 30 31 2E 78 6D 6C 0D 0A 41 63 63 65 70 74 2D 4C 01.xml Accept-L
16:23:54:104 [13] ThreadProcessConnection: 61 6E 67 75 61 67 65 3A 20 65 6E 0D 0A 58 2D 57 anguage: en X-W
16:23:54:136 [13] ThreadProcessConnection: 41 50 2D 4E 65 74 77 6F 72 6B 2D 43 6C 69 65 6E AP-Network-Clien
16:23:54:136 [13] ThreadProcessConnection: 74 2D 4D 53 49 53 44 4E 3A 20 2B 33 37 30 36 39 t-MSISDN: +37069
16:23:54:136 [13] ThreadProcessConnection: 39 32 33 33 30 30 0D 0A 0D 0A 923300
You'll note that there is no "Content-Length:" header in this message.
And there is also no "Transfer-encoding:" header in the message, which would be present if the HTTP request was chunked.
That is why we're responding back with a "500" error, because we don't know what to do with the request, as from our perspective, it is an empty post.
Try configuring the device to connect to the MMSC directly, and you'll see what I mean, as I expect the received request that the MMSC sees will be different (and will contain the expected MMS content).
In the meantime, also, you can configure that particular device to connect via a WSP/WAP bearer, which you should probably do until you get a working proxy.
-bn |
Search
Last
