Error code search

HTTP/2 ALTSVC frames are limited to a maximum of 16,382 payload bytes.

For HTTP/2 requests using the CONNECT method, the :authority pseudo-header is required.

For HTTP/2 requests using the CONNECT method, the :path pseudo-header is forbidden.

For HTTP/2 requests using the CONNECT method, the :scheme pseudo-header is forbidden.

A non-specific HTTP/2 error has occurred.

Used when a failure occurs sending an individual frame on the HTTP/2 session.

New HTTP/2 Streams may not be opened after the Http2Session has received a GOAWAY frame from the connected peer.

Additional headers were specified after an HTTP/2 response was initiated.

Used when an HTTP/2 Headers Object is expected.

An attempt was made to send multiple response headers.

Used when a required header is missing in an HTTP/2 message.

Multiple values were provided for an HTTP/2 header field that was required to have only a single value.

HTTP/2 informational headers must only be sent prior to calling the Http2Stream.prototype.respond() method.

Informational HTTP status codes (1xx) may not be set as the response status code on HTTP/2 responses.

HTTP/1 connection specific headers are forbidden to be used in HTTP/2 requests and responses.

An invalid HTTP/2 header value was specified.

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

HTTP/2 ORIGIN frames require a valid origin.

Input Buffer and Uint8Array instances passed to the http2.getUnpackedSettings() API must have a length that is a multiple of six.

Only valid HTTP/2 pseudoheaders (:status, :path, :authority, :scheme, and :method) may be used.

An action was performed on an Http2Session object that had already been destroyed.

An invalid value has been specified for an HTTP/2 setting.

An operation was performed on a stream that had already been destroyed.

Whenever an HTTP/2 SETTINGS frame is sent to a connected peer, the peer is required to send an acknowledgment that it has received and applied the new SETTINGS. By default, a maximum number of unacknowledged SETTINGS frames may be sent at any given time. This error code is used when that limit has been reached.

An attempt was made to initiate a new push stream from within a push stream. Nested push streams are not permitted.

Out of memory when using the http2session.setLocalWindowSize(windowSize) API.

An attempt was made to directly manipulate (read, write, pause, resume, etc.) a socket attached to an Http2Session.

HTTP/2 ORIGIN frames are limited to a length of 16382 bytes.

The number of streams created on a single HTTP/2 session reached the maximum limit.

A message payload was specified for an HTTP response code for which a payload is forbidden.

An HTTP/2 ping was canceled.

HTTP/2 ping payloads must be exactly 8 bytes in length.

An HTTP/2 pseudo-header has been used inappropriately. Pseudo-headers are header key names that begin with the : prefix.

An attempt was made to create a push stream, which had been disabled by the client.

An attempt was made to use the Http2Stream.prototype.responseWithFile() API to send a directory.

An attempt was made to use the Http2Stream.prototype.responseWithFile() API to send something other than a regular file, but offset or length options were provided.

The Http2Session closed with a non-zero error code.

The Http2Session settings canceled.

An attempt was made to connect a Http2Session object to a net.Socket or tls.TLSSocket that had already been bound to another Http2Session object.

An attempt was made to use the socket property of an Http2Session that has already been closed.