Open
Bug 1176518
Opened 9 years ago
Updated 2 years ago
Support multiple RTCCertificate values
Categories
(Core :: WebRTC: Signaling, defect, P4)
Core
WebRTC: Signaling
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox41 | --- | affected |
| backlog | webrtc/webaudio+ |
People
(Reporter: mt, Unassigned)
References
Details
(Whiteboard: dev-doc-needed)
Rather than just allow one, we could take one of each type and select the one that we like when needed.
|
||
Updated•9 years ago
|
backlog: --- → webRTC+
Rank: 35
Priority: -- → P3
|
||
Comment 1•8 years ago
|
||
May I ask what Firefox currently does if you specify multiple certificates? Does it error or does it just use the first one? This sounds like something that needs to be noted in documentation.
Whiteboard: dev-doc-needed
|
Reporter | |
Comment 2•8 years ago
|
||
It generates an error currently. Changes in NSS 3.24 will allow us to support >1 for servers, but not clients. This is going to take longer.
|
||
Comment 3•7 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•