Skip to content

Parse an IPv6 literal written inside brackets - #7

Merged
dominicletz merged 1 commit into
witchtails:masterfrom
neutrino38:fix/address-ipv6reference
Nov 2, 2026
Merged

dominicletz merged 1 commit into
witchtails:masterfrom
neutrino38:fix/address-ipv6reference

Conversation

@neutrino38

Copy link
Copy Markdown

That is the form a URI authority and a Host header carry an IPv6 literal in
(RFC 3986 §3.2.2), so it is the form a caller holding an address taken from a
URI has in hand. Every such caller had to strip the brackets itself, and the one
who forgot dialed the wrong address family with no diagnostic — the address just
looked like a host name that does not resolve.

The new clause reads the reference and delegates to the existing parser. Only a
v6 address is written that way, so "[127.0.0.1]" stays nil, and so does a
bracket that never closes.

Adds test/ipv6_test.exs with one test, over both the accepted and the rejected
spellings.

A URI authority and a Host header carry an IPv6 literal inside square
brackets (RFC 3986 §3.2.2), and that is the form a caller holding an
address taken from a URI has in hand. parse/1 answered nil on it, so
every such caller had to strip the brackets itself, and the one who
forgot dialed the wrong address family with no diagnostic.

Only a v6 address is written that way: "[127.0.0.1]" stays nil, and so
does a bracket that never closes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants