Variable StatusCodes2Const

Type declaration

• BadCertificateIssuerRevocationUnknown: node-opcua-status-code

  Could not verify the revocation status of the issuer Certificate.

• BadCertificateIssuerTimeInvalid: node-opcua-status-code

  The issuer for the sender Certificate has expired or is not yet valid.

• BadCertificateIssuerUseNotAllowed: node-opcua-status-code

  The issuer Certificate may not be used as a Certificate Authority.

• BadCertificateRevocationUnknown: node-opcua-status-code

  Could not verify the revocation status of the sender’s Certificate.

• BadCertificateRevoked: node-opcua-status-code

  The sender Certificate has been revoked by the issuer.

• BadCertificateTimeInvalid: node-opcua-status-code

  The sender Certificate has expired or is not yet valid.

• BadCertificateUntrusted: node-opcua-status-code

  The sender Certificate is not trusted by the receiver.

• BadCertificateUseNotAllowed: node-opcua-status-code

  The sender’s Certificate may not be used for establishing a secure channel.

• BadRequestInterrupted: node-opcua-status-code

  The request could not be sent because of a network interruption.

• BadRequestTimeout: node-opcua-status-code

  Timeout occurred while processing the request.

• BadSecureChannelClosed: node-opcua-status-code

  The secure channel has been closed.

• BadSecureChannelTokenUnknown: node-opcua-status-code

  The SecurityToken has expired or is not recognized. BadSecureChannelTokenUnknown

• BadSecurityChecksFailed: node-opcua-status-code

  The Message was rejected because it could not be verified.

• BadTcpEndpointUrlInvalid: node-opcua-status-code

  The Server does not recognize the EndpointUrl specified.

• BadTcpInternalError: node-opcua-status-code

  An internal error occurred. This should only be returned if an unexpected configuration or programming error occurs.

• BadTcpMessageTooLarge: node-opcua-status-code

  The size of the Message specified in the header is too large. The Server returns this error if the Message size exceeds its maximum buffer size or the receive buffer size negotiated during the Hello/Acknowledge exchange.

• BadTcpMessageTypeInvalid: node-opcua-status-code

  The type of the Message specified in the header invalid. Each Message starts with a 4-byte sequence of ASCII values that identifies the Message type. The Server returns this error if the Message type is not accepted. Some of the Message types are defined by the SecureChannel layer.

• BadTcpNotEnoughResources: node-opcua-status-code

  There are not enough resources to process the request. The Server returns this error when it runs out of memory or encounters similar resource problems. A Server can control the how frequently a Client reconnects by waiting to return this error.

• BadTcpSecureChannelUnknown: node-opcua-status-code

  The SecureChannelId and/or TokenId are not currently in use. This error is reported by the SecureChannel layer.

• BadTcpServerTooBusy: node-opcua-status-code

  The Server cannot process the request because it is too busy.

  It is up to the Server to determine when it needs to return this Message.

  A Server can control the how frequently a Client reconnects by waiting to return this error.

• BadTimeout: node-opcua-status-code

  A timeout occurred while accessing a resource. It is up to the Server to determine when a timeout occurs.