IPv6 zones in URLs are a mistake

TL;DR

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get the latest gadgets delivered free — and shop member deals

• Fast, free delivery on millions of items
• Access to Prime Big Deal Days deals on October 6–7
• Prime Video, Amazon Music and more included

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

IPv6 zone identifiers in URLs are problematic and not supported by browsers, leading to parsing errors. Experts warn this is an edge case that complicates URL handling and may require future standards updates.

Experts and developers have confirmed that including IPv6 zone identifiers in URLs is problematic and currently unsupported by browsers, complicating network address referencing and standard compliance.

Recent discussions on Hacker News and related developer forums have highlighted that IPv6 addresses with zone identifiers, such as fe80::4%eth0, cannot be properly represented in URLs without encoding issues. When attempting to include such addresses in URLs, errors occur because URLs do not natively support the ‘%’ character used for zone identifiers, requiring percent-encoding (e.g., %25) which complicates parsing and usability.

Major programming frameworks like Go’s net/url package and web browsers do not support IPv6 zone identifiers in URLs, citing RFC 3986 and RFC 9844, which lack clear guidance for such cases. This leads to errors, as seen in Go’s URL parsing failures, and browsers’ inability to handle these addresses, affecting applications that rely on link-local address referencing.

Why It Matters

This issue matters because it impacts network configuration, URL standardization, and the development of web and network tools. The inability to reliably include IPv6 zones in URLs hampers automation, debugging, and user interface design, potentially leading to misconfigurations or security concerns. Experts warn that unless standards evolve, this edge case will continue to cause interoperability issues.

Background

IPv6 introduced link-local addresses with zone identifiers to disambiguate interfaces on multi-interface devices. While these addresses are critical within local networks, their inclusion in URLs has been problematic since URL standards do not explicitly support zone identifiers. The issue has gained attention as developers encounter errors when trying to embed such addresses in web links, with ongoing discussions about RFC compliance and future standards.

“Including IPv6 zones in URLs is a terrible edge case that current standards and implementations poorly support, leading to errors and confusion.”

— Developer on Hacker News

What Remains Unclear

It is still unclear whether future standards will explicitly support IPv6 zone identifiers in URLs or if new encoding schemes will be adopted. The community is debating whether to update RFCs or develop alternative solutions, but no definitive timeline exists.

What’s Next

Next steps include ongoing discussions among standards bodies like IETF and W3C, potential updates to RFCs, and experimental implementations in browsers and frameworks. Developers are advised to avoid including zone identifiers in URLs until official support is established.

Key Questions

Why can’t I include IPv6 zone IDs directly in URLs?

URLs do not support the ‘%’ character used in zone IDs without percent-encoding, which causes parsing errors. Browsers and many frameworks currently do not support zone IDs in URLs for this reason.

Will future standards support IPv6 zones in URLs?

It is uncertain. Discussions are ongoing, and some experts suggest that future RFC updates may clarify or support such use cases, but no official timeline exists.

What should developers do now when referencing IPv6 addresses with zones?

Developers should avoid embedding zone identifiers in URLs or use percent-encoding (e.g., %25) if necessary, understanding that support remains limited and may cause compatibility issues.

Source: Hacker News