827789 - B2G MMS : The x-mms-content-location uri prePath from some cellphone operators is not the same as the MMSC in APN setting.

Status: RESOLVED DUPLICATE of bug 833697

(Core :: DOM: Device Interfaces, defect)

Description

[Chia-hung Tai [:ctai :ctai_mozilla :cht]]

In some cell phone operators, they might send MMs with x-mms-content-location uri which is totally different with the MMSC in their APN setting. It will cause the fail of receiving MM in some operators.

Comment 1

[Gene Lian (I already quit Mozilla)]

Just asking. Who decides the x-mms-content-location uri?

Comment 2

[Chia-hung Tai [:ctai :ctai_mozilla :cht]]

When cellphone A send a MM to Cellphone B, the MMSC of phone B will send a short message to point out the uri of x-mms-content-location. In some operators, the uri perPath will be the same as the MMSC. But some of operators are not. So we might need to design another way to register filter for the proxy, not pass the MmsService to the function registerFilter. Instead, we might encapsulate the process of dealing with MM as a transaction. The pass it to a transaction service. And pass the transaction to the function |registerFilter| if this transaction need the proxy to use http request.

Comment 3

[Chia-hung Tai [:ctai :ctai_mozilla :cht]]

Attachment: WIP