3

I've got a vhosts file set up for my local machine where I use a made up domain (cascade.mtn) with a bunch of subdomains (rainier.cascade.mtn, hood.cascade.mtn, etc). In every other browser I can hit those domains just fine but in Chrome it just takes me to a Google search.

Is there anyway to force Chrome to recognized the cascade.mtn domain?

ryanstewart
  • 1,004
  • 10
  • 18
  • Also, the first entry in my vhosts file is the rainier.cascade.mtn domain, and Chrome can load that one. So maybe it's something with the vhosts file? But that would affect other browsers too I assume. – ryanstewart Sep 22 '10 at 18:32

1 Answers1

9

Old question, but posting answer since I ran into the same thing.

If you add a trailing slash (/) to the end of the URL, it will hint Chrome to treat it as a URL, which is what you want. From that point, it will 'learn' that that is indeed a valid URL and you won't require the trailing slash anymore.

Jorge Israel Peña
  • 36,800
  • 16
  • 93
  • 123
  • You're welcome :D I was migrating to chrome myself and this was going to be a deal breaker, so I asked around on the dev IRC channel. – Jorge Israel Peña Dec 20 '10 at 08:23
  • what if my application does resolve paths with trailing slash differently than the ones without? your solution doesnt work for me – gondo Jan 21 '14 at 11:47