You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
After #12351, the server-side allocates the response headers using HttpConfiguration.responseHeaderSize.
However, #12544 introduced a more dynamic mechanism on the client-side where the generation of response headers is first tried with responseHeaderSize and in case of overflow, re-tried with maxResponseHeaderSize.
A similar mechanism should be added to the server-side.
The text was updated successfully, but these errors were encountered:
Jetty version(s)
12.0.x
Description
After #12351, the server-side allocates the response headers using
HttpConfiguration.responseHeaderSize
.However, #12544 introduced a more dynamic mechanism on the client-side where the generation of response headers is first tried with
responseHeaderSize
and in case of overflow, re-tried withmaxResponseHeaderSize
.A similar mechanism should be added to the server-side.
The text was updated successfully, but these errors were encountered: