Chrome – Does chrome process sites with www prefix differently


I host a number of sites from our partners. These sites are all subdomains of our partners top level domains. In response to the new push to https I have obtained certificates and created the appropriate bindings. All is good when the url:

is used. The request redirects to https and all is good. My issue at this point is when the url: is used.

In ie and Firefox the www remains and I get a certificate error (the cert is for not This I understand.
However, in chrome the www. is removed and the site loads correctly. Why is chrome different? There is no url rewrite on the site to remove www. Sites are hosted on iis 8.

As always any clarification is greatly appreciated

Related Question