Tested the issue on Android and able to reproduce this issue. 

Steps followed:
1. Launched chrome , Navigated to https://www.reddit.com/r/formula1/
2. Now again navigated to https://www.reddit.com/r/formula1 (without /)

Chrome versions tested:
70.0.3501.0

OS:
Android 9.0

Android Devices:
Pixel 2 XL

billdillensrevenge@: This might be due to your searches with https://www.reddit.com/r/formula1/ and https://www.reddit.com/r/formula1 (without slash). Could you please check by deleting those URLS from chrome history and re producing the steps. If issue is still reproducible feel free to ping back in this bug.
 
Thanks!

I completely cleared all history and went directly to both URL's (I didn't search them) and the issue is still present. There needs to be something to prevent effective duplicate URL's like this 

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested this issue on Android and able to reproduce this issue.

Steps Followed:
1.Launched chrome , navigated to https://reddit.com/r/forumla1 and https://reddit.com/r/forumla1/
2. Opened NTP and started typing https://reddit.com/r/for and observed both with slash and without slash as suggestions in omnibox

Chrome versions tested:
 60.0.3072.0, 67.0.3396.87(stable) ; 70.0.3501.0(canary)

OS:
Android 9.0

Android Devices:
Pixel 2 XL

This seems to be a Non-Regression issue as same behavior is seen from M-60 builds. Leaving the issue as Untriaged  for further input's on this issue.

Please navigate to below link for log's --
go/chrome-androidlogs/867170
 
Thanks!

drive-by: I can confirm this as well.

Chrome tries to eliminate duplicates when it knows the pages are actually duplicates.  In particular, it uses the test whether one page redirects to the other.  In this case, they don't!  (Bad, reddit, bad.)  Reddit serves two different pages that happen to look identical to the naked eye.

We could try do something smarter (fingerprint pages and compare fingerprints; look at URL similarity, or at least hostname similarity, etc.).  I'm a bit nervous about all this, as those things if done improperly can lead to security issues.  (Phishing page X gets marks as a duplicate of page Y; user types to go to X, presses enter, and doesn't realize they're at Y.)

Leave as untriaged to get us to think more about this and whether we want to do something here.  Demoting priority because it's not that systemic a problem.  (It'll mostly come from web sites that aren't assertive at sending users to their canonical URLs.)

"Reddit serves two different pages that happen to look identical to the naked eye."

This seems bad, should someone reach out to Reddit about this? 

> This seems bad, should someone reach out to Reddit about this? 
Sure.   Can you do it, since you were the one who found this issue?  Just kindly ask them to make the "without slash" version redirect to the "with slash" version (or vice versa), to make it clearer to web browsers that these pages are duplicates.

I don’t work for Google so I don’t think it would have anywhere near the same weight as a Googler asking them about this. Also, I didn’t know this is a reddit specific issue, I just uses reddit as an example, surely there are others? 

> I don’t work for Google so I don’t think it would have anywhere
> near the same weight as a Googler asking them about this.
I'm going to skip asking reddit because asking "as a Googler" would require getting permission from folks.  It's not worth the trouble.  Morphing this bug.

The short summary is that perhaps we should figure out some way to identify that pages are duplicates and suppress them, not merely suppressing redirects.  Maybe fingerprinting?  Maybe something else?  I'm not sure if this is possible, as many pages are entirely javascript-powered these days.

Leaving as open for now, though I wouldn't be surprised if the next person who attempts to triage this bug decides it's infeasible and WontFixes it.

@tedchoc - I'm not familiar with android-fe triage processes; per #12 should we mark this available or something besides triaged?

For the android triage process, we go through and look at the untriaged bugs and see if they need action on our part.  Based on the comment in #11, this seemed in a state of limbo.  Available implies we acknowledge the issue, so leaving it untriaged but not on our hopper of bugs to look at was the intent of that label.

go/chrome-android-frontend-triage for more info

thanks for the pointer!

>>>
I wouldn't be surprised if the next person who attempts to triage this bug decides it's infeasible and WontFixes it.
>>>

A month later, this bug is still in the omnibox triage queue.  (Tsk, tsk other triage engineers.)  So I'm the person who gets to make the decision.

I'm closing this as Infeasible.  I don't think there's a reasonable way to identify identical pages, as two pages can appear identical in HTML practice but differ based on time of day / how the Javascript interacts with the user's cookies / a variety of reasons.  Furthermore, it's unclear when to snapshot a page to compare for later, as pages change dynamically.  And I'm concerned that false positives (identifying a duplicate when there isn't one) can lead to misleading UIs, which can be security issues.  (A page Y.com manages to get Chrome to think it's a duplicate of bank page X.com, and then when a user tries to navigate to X.com, they may end up at Y.com without realizing it.)

P.S.  I reached out to reddit.