UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
1. Enter something, say, "politics" (no quotes) into the omnibox and press enter.
2. Repeat step one but accidentally hit the backslash (right above enter) before hitting enter which I would argue is a common mistake.  On pressing enter the backslash is autocorrected to a forward slash and Chrome treats it as navigation to a server, resulting in a Network Error (dns_server_failure) error.
3. Try to search "politics" again with no quotes.  AFTER hitting enter it is autocorrected to "politics/" and leads to the error.  I tried to specifically delete the forward slash but after pressing enter it autocompletes and throws an error.  I try adding a space after the search word but that gets autocorrected also.

What is the expected behavior?
I should be able to delete the forward slash from the end of the word in the omnibox, and press enter to search that word in a google search.  Chrome should learn that this is a mistake people make and stop the autocorrect from happening.

What went wrong?
The autocomplete prioritizes the accidental server navigation over the actual word that's typed regardless of frequency of use and the user's attempt to change it.  The workaround is to search something different, then use the google.com UI to search the word you want results for; which is very disruptive.

Did this work before? N/A 

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 10.0
Flash Version: