Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

getRemoteCertificates() behavior in "new" and "connecting" states #461

Closed
aboba opened this issue Jan 8, 2016 · 1 comment
Closed

getRemoteCertificates() behavior in "new" and "connecting" states #461

aboba opened this issue Jan 8, 2016 · 1 comment
Assignees
@aboba
Labels
PR exists

Comments

@aboba
Copy link
Contributor

aboba commented Jan 8, 2016

The specification does not describe what getRemoteCertificates() returns if it is called while RTCDtlsTransportState is "new" or "connecting". Where the remote peer offers multiple certificates, in the "new" or "connecting" state, the remote certificate may not yet have been selected.
@aboba aboba self-assigned this Jan 8, 2016
@aboba aboba mentioned this issue Jan 8, 2016
Merged
@stefhak
Copy link
Contributor

stefhak commented Jan 21, 2016

#460 has been merged, closing this issue.

@stefhak stefhak closed this as completed Jan 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aboba aboba

Labels
PR exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dontcallmedom @aboba @stefhak