Backport of Default ProxyType
for builtin extensions into release/1.16.x
#17667
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.
Backport
This PR is auto-generated from #17657 to be assessed for backporting due to the inclusion of the label backport/1.16.
The below text is copied from the body of the original PR.
Description
This PR updates the local rate limt, Lua and property override extensions to default the
ProxyType
input toconnect-proxy
since this is [currently] the only supported proxy type for these extensions. This aligns the default behavior across all builtin extensions that take aProxyType
and only supportconnect-proxy
.This is a non-breaking change since the config still allows setting the
ProxyType
expressly.Note that the docs have not been updated. I will update the docs in a separate PR once #17651 is merged.
Testing & Reproduction steps
Links
N/A
PR Checklist
Overview of commits