Conversation
Operators need a coherent path from enabling origin ALPN to evaluating HTTP/2 under production traffic. The individual record descriptions do not explain how flow control, pooling, and timeouts interact, or how to distinguish origin failures from unrelated changes in aggregate metrics. This guide explains per-route and global negotiation, fixed stream windows with policy 1, connection reuse, and timeout selection. It separates client-side tuning from origin settings and explains the tradeoffs behind deployment-specific values rather than prescribing a single configuration for every workload. The guide also describes origin protocol logging, separate HTTP/1 and HTTP/2 connection gauges, and a gradual rollout with error attribution. The flow-control discussion explains why dynamic stream-window SETTINGS can trigger origin rate limits and why policy changes require a restart. Related to apache#12175. Co-authored-by: GPT-6 Astra Medium
bneradt
force-pushed
the
document-http2-to-origin
branch
from
September 15, 2026 19:47
ccd4342 to
574335b
Compare
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.
Operators need a coherent path from enabling origin ALPN to evaluating
HTTP/2 under production traffic. The individual record descriptions do
not explain how flow control, pooling, and timeouts interact, or how to
distinguish origin failures from unrelated changes in aggregate metrics.
This guide explains per-route and global negotiation, fixed stream
windows with policy 1, connection reuse, and timeout selection. It
separates client-side tuning from origin settings and explains the
tradeoffs behind deployment-specific values rather than prescribing a
single configuration for every workload.
The guide also describes origin protocol logging, separate HTTP/1 and
HTTP/2 connection gauges, and a gradual rollout with error attribution.
The flow-control discussion explains why dynamic stream-window SETTINGS
can trigger origin rate limits and why policy changes require a restart.
Related to #12175.
Co-authored-by: GPT-6 Astra Medium