-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve buffer management of HTTP/1 response headers #12670
Comments
sbordet
added
the
Sponsored
This issue affects a user with a commercial support agreement
label
Jan 4, 2025
wendigo
added a commit
to airlift/airlift
that referenced
this issue
Jan 5, 2025
This circumvents jetty/jetty.project#12670
3 tasks
wendigo
added a commit
to airlift/airlift
that referenced
this issue
Jan 5, 2025
This circumvents jetty/jetty.project#12670
wendigo
added a commit
to airlift/airlift
that referenced
this issue
Jan 7, 2025
This circumvents jetty/jetty.project#12670
wendigo
added a commit
to wendigo/airlift
that referenced
this issue
Jan 9, 2025
This circumvents jetty/jetty.project#12670
wendigo
added a commit
to airlift/airlift
that referenced
this issue
Jan 13, 2025
This circumvents jetty/jetty.project#12670
wendigo
added a commit
to airlift/airlift
that referenced
this issue
Jan 14, 2025
This circumvents jetty/jetty.project#12670
wendigo
added a commit
to airlift/airlift
that referenced
this issue
Jan 14, 2025
This circumvents jetty/jetty.project#12670
wendigo
added a commit
to wendigo/airlift
that referenced
this issue
Jan 14, 2025
This circumvents jetty/jetty.project#12670
wendigo
added a commit
to airlift/airlift
that referenced
this issue
Jan 14, 2025
This circumvents jetty/jetty.project#12670
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: