| Content-type: */* necessary for reply to m-notifyresp-ind? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| L Wang New member Username: B2000 Post Number: 1 Registered: 09-2005 |
I'm using integrated MMSC of NOWSMS 5.51 with NOKIA's WAP gateways. Whenever the terminal successfully retrieves the MM, it would immediately post a m-notifyresp-ind onto the MMSC. The NOWSMS 5.51 would reply with a HTTP 200 reply indicating successful receipt of the indication. Though the content-length is 0, the header of "Content-Type: */*" confuses the NOKIA WAP Gateway as it cannot do a content adaption for */*. The WAP gateway simply drop the packet and give a negative reply to the terminal. Here is the snippet from MMSCDEBUG.LOG: 15:59:08:129 [7] ThreadProcessConnection: Got application/vnd.wap.mms-message 15:59:08:129 [7] ThreadProcessConnection: Got m-notifyresp-ind 15:59:08:129 [7] ThreadProcessConnection: HTTP/1.0 200 OK Connection: Close Content-Type: */* Content-Length: 0 Can any NOW experts tell me how to disable the "Content-Type" header? Or have it simply put as "Content-Type: application/vnd.wap.mms-message"? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5029 Registered: 10-2002 |
Hi, We added this "Content-type: */*" header originally because another WAP gateway didn't like it if no "Content-type:" header was present. In the WSP reply PDU, Content-type is a required field, whereas it is not required in HTTP. So the lack of a "Content-type:" header was causing the WAP gateway in question to generate an invalid PDU. We elected to put insert a "Content-type: */*" header because our WAP gateway uses this value when building a WSP reply PDU when no content type is present. (For no reason other than */* is the first value in one of the WSP tables.) I know this has worked fine with past Nokia WAP gateways, so I can only figure that Nokia has made further enhancements to that product. And personally, any "content adaptation" solution that throws away content that it cannot adapt (instead of passing it through) seems to explain why "content adaptation" solutions get such a bad reputation.... But I digress, and my opinion really doesn't matter because it doesn't solve the problem. We can change this to "Content-type: application/vnd.wap.mms-message". That shouldn't cause any problems ... but we will have to do some testing. I will post a reply here when an update is available (within this week). -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5084 Registered: 10-2002 |
Follow-up. We've posted an update to address this compatibility issue. This is reflected in v5.51j and later, which can currently be downloaded from http://www.nowsms.com/download/latestpatch.zip. The response has been changed to "Content-Type: application/vnd.wap.mms-message". -bn | |||
