Error code search

Use of the 101 Informational status code is forbidden in HTTP/2.

An invalid HTTP status code has been specified. Status codes must be an integer between 100 and 599 (inclusive).

An Http2Stream was destroyed before any data was transmitted to the connected peer.

Used when an action has been performed on an HTTP/2 Stream that has already been closed.

A non-zero error code was been specified in an RST_STREAM frame.

When setting the priority for an HTTP/2 stream, the stream may be marked as a dependency for a parent stream. This error code is used when an attempt is made to mark a stream and dependent of itself.

The number of supported custom settings (10) has been exceeded.

The limit of acceptable invalid HTTP/2 protocol frames sent by the peer, as specified through the maxSessionInvalidFrames option, has been exceeded.

The number of uniq origin sent by the server has exceeded the value defined in options.maxOriginSetSize.

Trailing headers have already been sent on the Http2Stream.

The http2stream.sendTrailers() method cannot be called until after the 'wantTrailers' event is emitted on an Http2Stream object. The 'wantTrailers' event will only be emitted if the waitForTrailers option is set for the Http2Stream.

http2.connect() was passed a URL that uses any protocol other than http: or https:.

An error is thrown when writing to an HTTP response which does not allow contents.

Response body size doesn't match with the specified content-length header value.

An attempt was made to add more headers after the headers had already been sent.

Used when an invalid character is found in an HTTP response status message (reason phrase).

An invalid HTTP header value was specified.

Status code was outside the regular status code range (100-999).

The client has not sent the entire request within the allowed time.

The given ServerResponse was already assigned a socket.

Changing the socket encoding is not allowed per RFC 7230 Section 3.

The Trailer header was set even though the transfer encoding does not support that.

An attempt was made to construct an object using a non-public constructor.

An import assertion has failed, preventing the specified module to be imported.

An import assertion is missing, preventing the specified module to be imported.

An import attribute is not supported by this version of Node.js.

An import attribute is missing, preventing the specified module to be imported.

An import type attribute was provided, but the specified module is of a different type.

An import attribute is not supported by this version of Node.js.

An option pair is incompatible with each other and cannot be used at the same time.

A given index was out of the accepted range (e.g. negative offsets).

The --input-type flag was used to attempt to execute a file. This flag can only be used with input via --eval, --print, or STDIN.

While using the node:inspector module, an attempt was made to activate the inspector when it already started to listen on a port. Use inspector.close() before activating it on a different address.

While using the node:inspector module, an attempt was made to connect when the inspector was already connected.

While using the node:inspector module, an attempt was made to use the inspector after the session had already closed.

An error occurred while issuing a command via the node:inspector module.

The inspector is not active when inspector.waitForDebugger() is called.

The node:inspector module is not available for use.

While using the node:inspector module, an attempt was made to use the inspector before it was connected.

An API was called on the main thread that can only be used from the worker thread.