Add ServeHttp11Action to selectively disable H2 serving#591
Merged
Conversation
When the global ServeH2 option is enabled, this new action allows selectively downgrading specific exchanges to HTTP/1.1 on the client-to-proxy connection via ALPN negotiation. Useful when certain clients or hosts are incompatible with HTTP/2 serving.
This was referenced Mar 30, 2026
This was referenced Apr 13, 2026
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
1 participant
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.
Summary
ServeHttp11Action, a new rule action that forces the downstream (client-to-proxy) connection to use HTTP/1.1 even when the globalServeH2option is enabledForceServeHttp11property toExchangeContextand wires it intoSecureConnectionUpdaterALPN negotiationMotivation
When
ServeH2is globally enabled, there was no way to selectively downgrade specific exchanges to HTTP/1.1 on the client side. This action allows per-rule control via the standard filter/action system, useful when certain clients or hosts are incompatible with HTTP/2 serving.