Http2Settings
Related Docs:
object Http2Settings
| package http2
Allows the sender to inform the remote endpoint of the maximum size of the header compression table used to decode header blocks, in octets.
Allows the sender to inform the remote endpoint of the maximum size of the header compression table used to decode header blocks, in octets. The encoder can select any size equal to or less than this value by using signaling specific to the header compression format inside a header block.
Indicates the sender's initial window size (in octets) for stream-level flow control.
Indicates the maximum number of concurrent streams that the sender will allow.
Indicates the maximum number of concurrent streams that the sender will allow. This limit is directional: it applies to the number of streams that the sender permits the receiver to create. Initially, there is no limit to this value. It is recommended that this value be no smaller than 100, so as to not unnecessarily limit parallelism.
A value of 0 for SETTINGS_MAX_CONCURRENT_STREAMS SHOULD NOT be treated as special by endpoints. A zero value does prevent the creation of new streams; however, this can also happen for any limit that is exhausted with active streams. Servers SHOULD only set a zero value for short durations; if a server does not wish to accept requests, closing the connection is more appropriate.
Indicates the size of the largest frame payload that the sender is willing to receive, in octets.
This advisory setting informs a peer of the maximum size of header list that the sender is prepared to accept, in octets.
This advisory setting informs a peer of the maximum size of header list that the sender is prepared to accept, in octets. The value is based on the uncompressed size of header fields, including the length of the name and value in octets plus an overhead of 32 octets for each header field.
This setting can be used to disable server push (Section 8.2).
A bundle of HTTP2 settings
These represent the HTTP2 settings for either the client or server.
https://tools.ietf.org/html/rfc7540#section-6.5.2, where the doc strings were obtained.