HTTP/2 max frame size exceeded when compression is used #24864
Labels
in:Transport
release bug
This bug is present in a released version of Open Liberty
release:23005
team:Sirius
Problem: When compression is configured in the server.xml on an httpendpoint and http/2 is used, the http/2 max frame size may be exceeded, leading to an http/2 FRAME_SIZE_ERROR in the server log.
Steps to Reproduce
Send an http/2 request to a server where the response data that is generated from the servlet, after compression, is larger than the http/2 MAX_FRAME_SIZE (default 16,384) of the client.
Expected behavior
The http/2 response data should be split into multiple data frames to avoid sending a data frame larger than the http/2 max frame size of the client.
Diagnostic information:
The client may observe a blank page after a request.
If cfw diagnostic trace is turned on, the following trace message may be seen in the log.
H2StreamProce 3 processNextFrame: DATA received on stream 1 is not a valid frame: FRAME_SIZE_ERROR
OpenLiberty Version: 18.0.0.2 - 23.0.0.4
Affected feature(s): servlet-4.0 with http/2 and compression
Java Version: n/a
server.xml configuration:
PH53475
The text was updated successfully, but these errors were encountered: