Sets the maximum dynamic table size for deflating header fields.
interface
http2.SessionOptions
interface SessionOptions
- maxHeaderListPairs?: number
Sets the maximum number of header entries. This is similar to
server.maxHeadersCount
orrequest.maxHeadersCount
in thenode:http
module. The minimum value is1
. - maxSendHeaderBlockLength?: number
Sets the maximum allowed size for a serialized, compressed block of headers. Attempts to send headers that exceed this limit will result in a
'frameError'
event being emitted and the stream being closed and destroyed. - maxSessionMemory?: number
Sets the maximum memory that the
Http2Session
is permitted to use. The value is expressed in terms of number of megabytes, e.g.1
equal 1 megabyte. The minimum value allowed is1
. This is a credit based limit, existingHttp2Stream
s may cause this limit to be exceeded, but newHttp2Stream
instances will be rejected while this limit is exceeded. The current number ofHttp2Stream
sessions, the current memory use of the header compression tables, current data queued to be sent, and unacknowledgedPING
andSETTINGS
frames are all counted towards the current limit. - maxSettings?: number
Sets the maximum number of settings entries per
SETTINGS
frame. The minimum value allowed is1
. - paddingStrategy?: number
Strategy used for determining the amount of padding to use for
HEADERS
andDATA
frames. - peerMaxConcurrentStreams?: number
Sets the maximum number of concurrent streams for the remote peer as if a
SETTINGS
frame had been received. Will be overridden if the remote peer sets its own value formaxConcurrentStreams
. - remoteCustomSettings?: number[]
The array of integer values determines the settings types, which are included in the
CustomSettings
-property of the received remoteSettings. Please see theCustomSettings
-property of theHttp2Settings
object for more information, on the allowed setting types. - unknownProtocolTimeout?: number
Specifies a timeout in milliseconds that a server should wait when an [
'unknownProtocol'
][] is emitted. If the socket has not been destroyed by that time the server will destroy it.