Closed
Bug 1373450
Opened 7 years ago
Closed 7 years ago
MaxMessageSize zero is ambiguous
Categories
(Core :: WebRTC: Signaling, enhancement, P2)
Core
WebRTC: Signaling
Tracking
()
RESOLVED
FIXED
mozilla56
Tracking | Status | |
---|---|---|
firefox56 | --- | fixed |
People
(Reporter: drno, Assigned: drno)
References
Details
Attachments
(1 file)
As a client is allowed to set 0 as it's a=max-message-size value it is not clear if the client provided the value at all or not. But we need that knowledge to differentiate between old and new Firefox versions.
Assignee | ||
Updated•7 years ago
|
Rank: 25
Comment hidden (mozreview-request) |
Comment 2•7 years ago
|
||
mozreview-review |
Comment on attachment 8878240 [details] Bug 1373450: report if MaxMessageSize was set in SDP. https://reviewboard.mozilla.org/r/149584/#review154330
Attachment #8878240 -
Flags: review?(rjesup) → review+
Pushed by drno@ohlmeier.org: https://hg.mozilla.org/integration/autoland/rev/757aa3bdc2dd report if MaxMessageSize was set in SDP. r=jesup
Comment 4•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/757aa3bdc2dd
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox56:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla56
You need to log in
before you can comment on or make changes to this bug.
Description
•