Closed Bug 1067637 Opened 10 years ago Closed 10 years ago

Navigating to "172.16.141.50:8080" does a keyword search instead of loading the host:port address

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1067168

People

(Reporter: sydpolk, Unassigned)

References

Details

I have a web server on a local VM. On Nightly (35), when I try to navigate to it, it tries to search for it instead. On Aurora (34), it works fine.
Gijs, might this be a regression due to recent changes to uri fixup?
Flags: needinfo?(gijskruitbosch+bugs)
Is this a duplicate of bug 1067168?
(tweaking summary to be more clear) (In reply to Tim Taubert [:ttaubert] from comment #2) > Is this a duplicate of bug 1067168? I doubt bug 1067168 as-is will fix this issue. (In reply to Marco Bonardo [::mak] (needinfo? me) from comment #1) > Gijs, might this be a regression due to recent changes to uri fixup? This seems likely. Alex, can you take a look?
Blocks: 494092
Flags: needinfo?(gijskruitbosch+bugs) → needinfo?(abardas)
Summary: Navigating to http://172.16.141.50:8080 tries to Google instead → Navigating to "172.16.141.50:8080" does a keyword search instead of loading the host:port address
(In reply to :Gijs Kruitbosch from comment #3) > (tweaking summary to be more clear) > > (In reply to Tim Taubert [:ttaubert] from comment #2) > > Is this a duplicate of bug 1067168? > > I doubt bug 1067168 as-is will fix this issue. > > (In reply to Marco Bonardo [::mak] (needinfo? me) from comment #1) > > Gijs, might this be a regression due to recent changes to uri fixup? > > This seems likely. Alex, can you take a look? It's a regression from bug 494092. I've added the fix for this bug in the new patch for bug 1067168. I'd prefer to fix there both cases, instead of having multiple rebased patches, if this is ok.
Flags: needinfo?(abardas)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.