fix: set SchemeHeaderTransformation.MatchUpstream on AI Gateway listeners - #2194
Merged
Conversation
…ners Signed-off-by: Anurag Aggarwal <kanurag94@gmail.com>
dosubot
Bot
added
the
size:XS
nacx
approved these changes
Jun 10, 2026
nacx
enabled auto-merge (squash)
June 10, 2026 09:58
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2194 +/- ##
==========================================
+ Coverage 84.50% 84.69% +0.19%
==========================================
Files 144 144
Lines 21055 21057 +2
==========================================
+ Hits 17792 17835 +43
+ Misses 2188 2143 -45
- Partials 1075 1079 +4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Member
|
/retest |
hustxiayang
pushed a commit
to hustxiayang/ai-gateway
that referenced
this pull request
Jun 12, 2026
…ners (envoyproxy#2194) **Description** Azure is strict about `scheme` header to be same as the TLS transport on which the request is being made. If the listener is an http listener, envoy forwards a request with `scheme: http` instead of `https`. This leads to requests getting dropped. The simple solution is to use `matchUpstream` which is what is being done in MCP backend listeners but missed in regular AI gateway route listeners. **Related Issues/PRs (if applicable)** Fixes envoyproxy#2095 Signed-off-by: Anurag Aggarwal <kanurag94@gmail.com> Signed-off-by: yxia216 <yxia216@bloomberg.net>
hustxiayang
pushed a commit
to hustxiayang/ai-gateway
that referenced
this pull request
Jun 16, 2026
…ners (envoyproxy#2194) **Description** Azure is strict about `scheme` header to be same as the TLS transport on which the request is being made. If the listener is an http listener, envoy forwards a request with `scheme: http` instead of `https`. This leads to requests getting dropped. The simple solution is to use `matchUpstream` which is what is being done in MCP backend listeners but missed in regular AI gateway route listeners. **Related Issues/PRs (if applicable)** Fixes envoyproxy#2095 Signed-off-by: Anurag Aggarwal <kanurag94@gmail.com> Signed-off-by: yxia216 <yxia216@bloomberg.net>
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
3 participants
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.
Description
Azure is strict about
schemeheader to be same as the TLS transport on which the request is being made. If the listener is an http listener, envoy forwards a request withscheme: httpinstead ofhttps. This leads to requests getting dropped.The simple solution is to use
matchUpstreamwhich is what is being done in MCP backend listeners but missed in regular AI gateway route listeners.Related Issues/PRs (if applicable)
Fixes #2095