QHttp2Configuration#

The QHttp2Configuration class controls HTTP/2 parameters and settings. More…

Synopsis#

Functions#

def huffmanCompressionEnabled ()
def maxFrameSize ()
def __ne__ (rhs)
def __eq__ (rhs)
def serverPushEnabled ()
def sessionReceiveWindowSize ()
def setHuffmanCompressionEnabled (enable)
def setMaxFrameSize (size)
def setServerPushEnabled (enable)
def setSessionReceiveWindowSize (size)
def setStreamReceiveWindowSize (size)
def streamReceiveWindowSize ()
def swap (other)

Note

This documentation may contain snippets that were automatically translated from C++ to Python. We always welcome contributions to the snippet translation. If you see an issue with the translation, you can also let us know by creating a ticket on https:/bugreports.qt.io/projects/PYSIDE

Detailed Description#

QHttp2Configuration controls HTTP/2 parameters and settings that QNetworkAccessManager will use to send requests and process responses when the HTTP/2 protocol is enabled.

The HTTP/2 parameters that QHttp2Configuration currently supports include:

The session window size for connection-level flow control. Will be sent to a remote peer when needed as ‘WINDOW_UPDATE’ frames on the stream with an identifier 0.

The stream receiving window size for stream-level flow control. Sent as ‘SETTINGS_INITIAL_WINDOW_SIZE’ parameter in the initial SETTINGS frame and, when needed, ‘WINDOW_UPDATE’ frames will be sent on streams that QNetworkAccessManager opens.

The maximum frame size. This parameter limits the maximum payload a frame coming from the remote peer can have. Sent by QNetworkAccessManager as ‘SETTINGS_MAX_FRAME_SIZE’ parameter in the initial ‘SETTINGS’ frame.

The server push. Allows to enable or disable server push. Sent as ‘SETTINGS_ENABLE_PUSH’ parameter in the initial ‘SETTINGS’ frame.

The QHttp2Configuration class also controls if the header compression algorithm (HPACK) is additionally using Huffman coding for string compression.

Note

The configuration must be set before the first request was sent to a given host (and thus an HTTP/2 session established).

Note

Details about flow control, server push and ‘SETTINGS’ can be found in RFC 7540 . Different modes and parameters of the HPACK compression algorithm are described in RFC 7541 .