| Retrieve.conf error |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through February 03, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hi folks, If I receive a WSP GET request to retrieve an MMS and there is a problem (not exists, It was deleted...) ==> two questions: 1) I have to send a well formed retrieve.conf with: - X-Mms-Retrieve-Status= 224 (i.e.error-permanent-failure) ?? CASE A or I have to send a 'Data not available' status code (404) via HTTP ?? CASE B 2) and If I must send a retrieve.conf (CASE A) there are mandatory fields for it: message-type, version, date and content-type. The last one (content-type) goes with the other fields ??? 8c 84 (type: retrieve.conf) 8D 90 (version: 1.0) 85 ... (Date: ...) 99 ... (Retrieve-Status: ....) XX YY (Content-Type: value) or if I send a HTTP Header like header("Content-Type: application/vnd.wap.mms-message"); is It suffice ? If content-type goes with the other header fields what are XX YY values ?? If the correct CASE is B, any example ?? Thank you very much | |||
| Murali Mohan.K Unregistered guest |
Hi Anonymous, If you see the MMS 1.1 spec conformance for MMS Client, X-Mms-Retrieve-Status field is optional. That means not all MMS Clients may handle even if you set this field. So it will be a good idea to opt for CASE B. Also if you use CASE A, you will have to send another notification msg to the client to download the MMS, which is not so good. So I feel the 'Data not available' status code (404) via HTTP option is the best with which the client can immediately know the status. Let me also know if you have some other view on this. Cheers Murali | |||
