Fix strategies to initialize scheme #8650
Merged
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.
This makes strategies (both core and plugin) default initialize the scheme to NONE.
Without this, omitting the scheme in strategies.yaml causes an assertion failure during a runtime request.
With this, a strategy with no scheme specified will match a host with no scheme, allowing users to omit the scheme.
This "scheme" is only ever used to match strategies to hosts, the actual scheme requested of the parent is the remap target.
This also updates the docs to note the scheme is only used to match, not request, and that it's optional.