Accept leading zeros in IPv4-mapped IPv6 #568
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
Relax pattern for mapped IPv4 octets (≤255); standalone IPv4 rules unchanged.
ok2c
approved these changes
Oct 11, 2025
ok2c
pushed a commit
that referenced
this pull request
Dec 6, 2025
Relax pattern for mapped IPv4 octets (≤255); standalone IPv4 rules unchanged.
ok2c
pushed a commit
that referenced
this pull request
Dec 7, 2025
Relax pattern for mapped IPv4 octets (≤255); standalone IPv4 rules unchanged.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Update IPV4_MAPPED_IPV6_PATTERN to allow redundant leading zeros in the IPv4 portion of IPv4-mapped IPv6 addresses (e.g., ::ffff:001.002.003.004) while keeping standalone IPv4 validation strict. Includes unit tests covering valid zero-padded forms and representative invalid inputs