fix(http): validate Origin literals and cache known schemas - #1319
Open
GraciousGazelles wants to merge 2 commits into
Open
GraciousGazelles wants to merge 2 commits into
GraciousGazelles wants to merge 2 commits into
Conversation
github-actions
Bot
added
T-test
This branch has not been deployed
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.
Unknown tool names were retained as negative schema-cache entries before request rejection. The cache now retains only successful schema lookups, preserving shared positive results while allowing unknown names and failed service lookups to be retried without persistent entries.
The HTTP Origin validator now rejects duplicate fields and malformed serialized authorities before URI component extraction. Complete IP-literal and port checks preserve valid IPv6/IPvFuture, default-port, absent-Origin and configured allowlist behavior.
Regression coverage uses the existing cache and HTTP transport seams: repeated distinct misses and factory failures, shared positive lookups, matching-allowlist malformed Origin cases, duplicate fields, and valid literal/default-port controls. No dependency or public API changes.
Validation: formatting and diff checks passed. Native hosted CI is pending; the no-local-feature test lane is required to execute the HTTP implementation and its regressions.