On 22/11/2023 13:11, Sandeep Gaur wrote:
Hi All/Oleg,
Greetings everyone! I trust you are all doing well. We've been utilizing
httpcore5-h2 (version 5.2.2), and unfortunately, we encountered an issue
in our production environment yesterday. Upon investigation of the
library code, it appears that the problem lies within the library.
The Issue: HTTP calls to send a file larger than 16KB are failing due to
an error stating, "Frame size exceeds maximum."
Background: Our server is accessed behind an Application Load Balancer
(ALB). We previously faced an issue where the frame size was set to
16MB, as dictated by the remote configuration, leading to memory
problems. This particular issue was addressed in a previous resolution:
https://issues.apache.org/jira/browse/HTTPCORE-751
<https://issues.apache.org/jira/browse/HTTPCORE-751>. In that
resolution, we agreed to use a smaller frame size, expecting that the
server would not send frames larger than the specified size.
I believe that the current issue may be a regression resulting from the
changes implemented in
https://issues.apache.org/jira/browse/HTTPCORE-751
<https://issues.apache.org/jira/browse/HTTPCORE-751>.
image.png
if you look at the code highlighted above in AbstractH2StreamMultiplexer
class, it should be
final int maxPayloadSize =Math.min(capacity, localConfig.getMaxFrameSize());
because we have set it value between the minimum of both server and local
config otherwise payload can exceed the outBuffer size which is happening in
our case.
Sandeep
Please post the complete wire log (including frame content) of the
session. However I strongly suspect this is a server-side error. The
server is not supposed to send frames larger than 16KB if the client
signaled it is not willing to accept frames larger than 16KB during the
settings handshake.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
