| Problem sending MMS Notification to a PPG: 400 bad Request |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hello, we recently purchased a NowMMS SMS/MMS Gateway v5.51, and tried to configure it according to your technical bulletin to send MMS notifications through PAP. The apache of the target PPG is always responding "400 Bad Request". After some investigation, it appears that the line of the request that cause this behaviour is: Content-Type: multipart/related; boundary="--mime-boundary-wap-push-19B575BE"; type=application/xml And the line that works is: Content-Type: multipart/related; boundary="--mime-boundary-wap-push-19B575BE"; type="application/xml" Notice the: type="application/xml". Is there a way to configure NowMMS to change this HTTP header ? I can provide full traces through mail if needed. Best regards, | |||
| Anonymous |
Just another piece of information, I have manually saved the request from NowMMS, added the '"' around "application/xml" and sent the request again to the PPG and it is accepted. This confirms the problem. Furthermore, on all traces I've seen over this forum, NowMMS seems to set those '"'. Is there a known problem with the 5.51 version of NowMMS ? Best regards | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3963 Registered: 10-2002 |
You're correct. According to the MIME specification, the "type=" parameter value in a "Content-type:" header needs to be a quoted string. (RFC 2045, Section 5.1) Technically the parameter value can be either a token or a quoted string. But the problem is that a token cannot contain any white space characters or characters that are characterised as "tspecials". The "/" character is one of the "tspecials", therefore technically this needs to be a quoted string. I'm surprised that a PPG would be that picky, but technically we are wrong here. I'm posting an update to http://www.nowsms.com/download/latestpatch.zip. Also, if anyone is reading this thread and has no idea what I'm talking about, it is referring to a configuration where NowSMS is an MMSC, and it is delivering MMS Notifications through a separate WAP Push Proxy Gateway (PPG). This configuration is described at http://www.nowsms.com/support/bulletins/tb-nowsms-007.htm. -bn | |||
| Anonymous |
Thank you for your quick and accurate answer. I have successfully installed the patch and it is now running well. Best Regards | |||
