Closed Bug 1651846 Opened 4 years ago Closed 4 years ago

link-local IPv6 address with interface not recognized

Categories

(Firefox :: Address Bar, defect)

70 Branch
defect
Points:
2

Tracking

()

RESOLVED DUPLICATE of bug 700999
Iteration:
80.2 - July 13 - July 26

People

(Reporter: philipp-blum, Assigned: mak)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

Type in a link-local IPv6 with interface into the address bar of Firefox.
Like: http://[fe80::ee08:6bff:fe5a:cbe2%wlp3s0]/
The browser is not recognizing it as a correct IPv6 and redirects to the search engine. According to the IPv6 specs, this is a valid address and should be treated accordingly.

Actual results:

Searchs for the URL in the search engine

Expected results:

Showing the requested resource

Has STR: --- → yes
Component: Untriaged → Address Bar

it looks like we don't properly recognize the scope (https://tools.ietf.org/html/rfc4007)

Assignee: nobody → mak
Severity: -- → S2
Status: UNCONFIRMED → ASSIGNED
Iteration: --- → 80.2 - July 13 - July 26
Points: --- → 2
Ever confirmed: true
Priority: -- → P1

Valentin, it looks like also the url parser doesn't like this, new URL("http://[fe80::ee08:6bff:fe5a:cbe2%wlp3s0]/") is failing. Is that expected?

Flags: needinfo?(valentin.gosu)

Yes, the URL parser (https://url.spec.whatwg.org/) doesn't accept interfaces.
Chrome behaves the same.

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Flags: needinfo?(valentin.gosu)
Resolution: --- → DUPLICATE

Resetting priority/severity to avoid upcoming needinfo spam on the dupe target, via https://github.com/mozilla/relman-auto-nag/pull/1672

Severity: S2 → --
Priority: P1 → --
You need to log in before you can comment on or make changes to this bug.