The default bug view has changed. See this FAQ.

nsWebSocketEstablishedConnection should implement securityInfo attribute

RESOLVED FIXED

Status

()

Core
Networking: WebSockets
RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: mayhemer, Assigned: mcmanus)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
I just discovered that nsWebSocketEstablishedConnection throws NS_NOT_IMPLEMENTED when accessing securityInfo readonly attribute though it keeps reference to the socket transport where from we can easily obtain the security info.

When the web socket instance is secure it reports it self as non-secure, I don't think it is a good idea.

If anybody doesn't object I'll implement the method properly.
(Assignee)

Comment 1

6 years ago
in the websockets -06 patch, nsWebSocketEstablishedConnection no longer implements nsIChannel - so strictly speaking it makes this a nop.

That same patch introduces nsIWebSocketProtocol, which largely plays the role of what established connection used to do, and that idl does define and implement the securityInfo attribute.
Assignee: nobody → mcmanus
Status: UNCONFIRMED → ASSIGNED
Component: Networking → Networking: WebSockets
Depends on: 640003
Ever confirmed: true
QA Contact: networking → networking.websockets
(Assignee)

Comment 2

6 years ago
fixed as part of 640003
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.