Closed
Bug 887646
Opened 11 years ago
Closed 11 years ago
B2G MMS: Do not set content-length in smil header when sending.
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
People
(Reporter: ctai, Assigned: ctai)
References
Details
(Whiteboard: [fixed-in-birch])
Attachments
(1 file)
991 bytes,
patch
|
airpingu
:
review+
|
Details | Diff | Splinter Review |
We don't need to set set content-length in smil header when sending. In some operators they will rewrite the smil. If we set content-length, some operators might skip the recalculating of new smil.
Assignee | ||
Comment 2•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Attachment #768165 -
Flags: review?(gene.lian)
Comment 4•11 years ago
|
||
Comment on attachment 768165 [details] [diff] [review] Patch v1.0 Review of attachment 768165 [details] [diff] [review]: ----------------------------------------------------------------- It doesn't solve the real problem at bug 883019, but anyway we shouldn't set the SMIL.length as the content-length because the new length of the utf-8 encoding SMIL could be different. Removing this can also solve this potential issue. Please do make sure this won't create any other regressions before landing.
Attachment #768165 -
Flags: review?(gene.lian) → review+
Assignee | ||
Updated•11 years ago
|
blocking-b2g: leo+ → leo?
Keywords: checkin-needed
Updated•11 years ago
|
blocking-b2g: leo? → leo+
Comment 5•11 years ago
|
||
https://hg.mozilla.org/projects/birch/rev/7c34ca069742 https://hg.mozilla.org/releases/mozilla-b2g18/rev/707ffca0b100
status-b2g18:
--- → fixed
status-b2g18-v1.0.0:
--- → wontfix
status-b2g18-v1.0.1:
--- → wontfix
status-b2g-v1.1hd:
--- → affected
Keywords: checkin-needed
Whiteboard: [fixed-in-birch]
Comment 6•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/7c34ca069742
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla25
Comment 7•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g18_v1_1_0_hd/rev/707ffca0b100
You need to log in
before you can comment on or make changes to this bug.
Description
•