Closed
Bug 884146
Opened 12 years ago
Closed 12 years ago
B2G MMS: Can not receive MMS from FarEasTone sim card.
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
People
(Reporter: ctai, Assigned: ctai)
References
Details
(Whiteboard: [fixed-in-birch])
Attachments
(1 file)
2.66 KB,
patch
|
vicamo
:
review+
|
Details | Diff | Splinter Review |
Can not receive MMS from Far-stone sim card. Http request done, but will get an http status 400.
Assignee | ||
Updated•12 years ago
|
No longer blocks: b2g-mms
Summary: B2G MMS: Can not receive MMS from Far-stone sim card. → B2G MMS: Can not receive MMS from FarEasTone sim card.
Assignee | ||
Comment 1•12 years ago
|
||
After some experiments, root cause is we need HOST when GET HTTP request.
Below is the successful step.
busybox telnet 210.241.199.199 9201
GET http://10.76.148.161/servlets/mms?message-id=mxvhKjo1y01 HTTP/1.1
HOST:10.76.148.161
Assignee | ||
Comment 2•12 years ago
|
||
You can print buf in the function nsHttpConnection::OnReadSegment.
See below:
nsresult nsHttpConnection::OnReadSegment(const char *buf,
uint32_t count,
uint32_t *countRead)
https://mxr.mozilla.org/mozilla-central/source/netwerk/protocol/http/nsHttpConnection.cpp#1185
Assignee | ||
Comment 3•12 years ago
|
||
The root cause is we set the ContentLength:0 in GET method. Looks like the MMS proxy in FarEasTone can not accept it. Maybe other operators also have those kind of behaviour. Nominate to leo+.
blocking-b2g: --- → leo?
Assignee | ||
Comment 4•12 years ago
|
||
Assignee | ||
Updated•12 years ago
|
Attachment #764060 -
Flags: review?(vyang)
Updated•12 years ago
|
Attachment #764060 -
Flags: review?(vyang) → review+
Comment 5•12 years ago
|
||
Whiteboard: [fixed-in-birch]
Comment 6•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla24
Comment 7•12 years ago
|
||
Triage - leo+ as agreed with partners based on comment 3
blocking-b2g: leo? → leo+
Comment 8•12 years ago
|
||
status-b2g18:
--- → fixed
status-b2g18-v1.0.0:
--- → wontfix
status-b2g18-v1.0.1:
--- → wontfix
status-b2g-v1.1hd:
--- → affected
status-firefox22:
--- → wontfix
status-firefox23:
--- → wontfix
status-firefox24:
--- → fixed
Comment 9•12 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•