Raise HTTP/2 SETTINGS limits - #13444
Merged
Merged
Conversation
HTTP/2 extensions can add enough SETTINGS parameters to exceed the defaults, causing Traffic Server to close otherwise valid connections before a request. This occurs with Meta forward proxy traffic that advertises WebTransport-over-HTTP/2 settings. This raises the per-frame limit to 16 and the per-minute limit to 32, retaining abuse protections while allowing protocol growth. This also adds an AuTest that sends an extension-rich SETTINGS frame and verifies that the subsequent request succeeds. Fixes: apache#13443
bneradt
force-pushed
the
raise-http2-settings-limits
branch
from
July 29, 2026 15:30
3695f54 to
219988b
Compare
maskit
approved these changes
Jul 30, 2026
maskit
left a comment
maskit
left a comment
Member
There was a problem hiding this comment.
I"m fine with the new limits (still small enough), but at the same time I'm not sure what are reasonable limits. We probably don't want to make the default values 1000 even if there is a legitimate case. The default values should be safe, and settings should be adjusted by users for minor use cases.
cmcfarlen
pushed a commit
that referenced
this pull request
Aug 4, 2026
HTTP/2 extensions can add enough SETTINGS parameters to exceed the defaults, causing Traffic Server to close otherwise valid connections before a request. This occurs with Meta forward proxy traffic that advertises WebTransport-over-HTTP/2 settings. This raises the per-frame limit to 16 and the per-minute limit to 32, retaining abuse protections while allowing protocol growth. This also adds an AuTest that sends an extension-rich SETTINGS frame and verifies that the subsequent request succeeds. Fixes: #13443 (cherry picked from commit 89fdedb)
Contributor
|
Cherry-picked to the 10.2.x branch as 53f07be for the 10.2.0 release. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HTTP/2 extensions can add enough SETTINGS parameters to exceed the
defaults, causing Traffic Server to close otherwise valid connections
before a request. This occurs with Meta forward proxy traffic that
advertises WebTransport-over-HTTP/2 settings.
This raises the per-frame limit to 16 and the per-minute limit to
32, retaining abuse protections while allowing protocol growth. This
also adds an AuTest that sends an extension-rich SETTINGS frame and
verifies that the subsequent request succeeds.
Fixes: #13443