Readonly
KEAKeyReadonly
KEAUsedReadonly
MACAlgorithmReadonly
SSLVersionReadonly
SSLVersionReadonly
clientTrue iff a client cert has been sent to the server - i.e. this socket has been client-cert authenticated.
If set to true before the server requests a client cert no cert will be sent.
Readonly
earlyIf 0RTT handshake was applied and some data has been sent, as soon as the handshake finishes this attribute will be set to appropriate value.
echConfig is defined for conveying the ECH configuration. This is encoded in base64.
esniTxt is a string that consists of the concatenated _esni. TXT records. This is a base64 encoded ESNIKeys structure.
Readonly
failedfailedVerification is true if any enforced certificate checks have failed. Connections that have not yet tried to verify, or are using acceptable exceptions will all return false.
Readonly
peerThe id used to uniquely identify the connection to the peer.
Readonly
providerThe original flags from the socket provider.
Readonly
retryThe echConfig that should be used to retry for the connection setup.
Readonly
securityThe securityInfo of the TLS handshake.
Optional
aInstancePtr: objectA run time mechanism for interface discovery.
NS_OK if the interface is supported by the associated instance, NS_NOINTERFACE if it is not.
aInstancePtr must not be null.
[in] A requested interface IID
[out] A pointer to an interface pointer to receive the result.
Determine if a potential SSL connection to hostname:port with a desired NPN negotiated protocol of npnProtocol can use the socket associated with this object instead of making a new one. And if so, combine them.
NPN (Next Protocol Negotiation) is a mechanism for negotiating the protocol to be spoken inside the SSL tunnel during the SSL handshake. The NPNList is the list of offered client side protocols. setNPNList() needs to be called before any data is read or written (including the handshake to be setup correctly. The server determines the priority when multiple matches occur, but if there is no overlap the first protocol in the list is used.
Generated using TypeDoc
The Key Exchange Algorithm is used when determining whether or not HTTP/2 can be used.
After a handshake is complete it can be read from KEAUsed. The values correspond to the SSLKEAType enum in NSS or the KEY_EXCHANGE_UNKNOWN constant defined below.
KEAKeyBits is the size/security-level used for the KEA.