fix: accept bare host URLs#138
Merged
Merged
Conversation
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
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.
What
Allow fetchkit web fetch requests to accept browser-like bare domain URLs such as
paseo.sh/docs/custom-providersby normalizing them tohttps://paseo.sh/docs/custom-providersbefore validation and execution.Why
Host integrations should not need wrappers for common URL input. fetchkit owns the request contract, URL validation, schema/help text, and SSRF/prefix policy enforcement.
How
FetchRequestbefore tool, client, registry, and save-to-file execution paths.http://andhttps://URLs as provided.Risk
InvalidUrlScheme; callers relying on that exact rejection for domain-like inputs may need to account for the new accepted form.Checklist