| [MMSC] Error codes returned in HTTP responses |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ Archive through October 01, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| Ivan Thomas New member Username: Ithomasfr Post Number: 3 Registered: 05-2004 |
Dear support, I am a customer of your MMSC solution. Here is one question on how it manages the errors sent in the response of the HTTP POST (for MO MMS) or HTTP GET (for MT MMS) requests. Does the MMSC put the error code (e.g. user is not provisioned, MMSE format is not correct or MMS ID doesn't exist for a MT MMS) in the HTTP error code or in the MMSE error code (X-MMS-Response-Status field)? Thanks in advance. Best regards, Ivan Thomas Customer Project Manager VoluBill Professional Services _________________________ www.volubill.com 80, allée Saint Exupéry F-38330 Montbonnot Saint-Martin Cedex (FRANCE) Direct: +33 4 76 04 37 33 Mobile: +33 6 23 79 09 52 Fax: +33 4 76 04 37 98 | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7197 Registered: 10-2002 |
Hello Ivan, The way that the MMSC specification is defined, an MMS specific error will not result in a non-OK HTTP error code. Unless the error is not an MMS specific error (like a completely invalid request, or a file not found when retrieving MMS content), the HTTP error code is going to be 200 or 204, which are both OK responses. (I don't think we send 204 because it confuses some WAP gateways.) So if there is an MMS specific error, you're generally going to get an MMS response back with the X-MMS-Response-Status header set (and sometimes X-MMS-Response-Text will also be set to provide more information). But in the case of MT MMS, if the message id is invalid, you would see an HTTP 404 (Not Found) error. -bn | |||
