Repository navigation
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.
Fixes #91's validation case.
uri_reference('.://').is_valid()currently returnsTrue, andValidator().check_validity_of('path')accepts the same invalid relative reference. RFC 3986 §4.2 forbids a colon in the first path segment of a reference without a scheme.Apply that contextual rule in both the configured validator and the legacy URI validation methods. Parsing remains permissive, consistent with the existing separation of parsing and validation. Standalone
path_is_valid()keeps its component-only behavior, since a colon is valid in a rootless path when a scheme is present. Legal references such asurn:a:b,./a:b,/a:b, and percent-encoded colons remain valid.Validation on Linux / Python 3.12:
This branch is based directly on
mainand is independent of #159.