Chrome dropping www subdomain on request
I have currently setup a website with a ssl cert which does not support wildcards and points to the bare domain. Upon testing the URL on different browsers I noticed that when requesting the domain with the www subdomain (https://www ... ), which is not supported by the certificate, gets a response in chrome. So I looked up the requested url in the dev tools and found that chrome does request the url without the www subdomain. Is this normal behavior for Chrome?
On other browsers this behavior is not occurring. In Firefox and Internet Explorer I get the expected certificate error.
google-chrome ssl https ssl-certificate
asked Jan 30 at 14:16
user3657850user3657850
1
add a comment |
I have currently setup a website with a ssl cert which does not support wildcards and points to the bare domain. Upon testing the URL on different browsers I noticed that when requesting the domain with the www subdomain (https://www ... ), which is not supported by the certificate, gets a response in chrome. So I looked up the requested url in the dev tools and found that chrome does request the url without the www subdomain. Is this normal behavior for Chrome?
On other browsers this behavior is not occurring. In Firefox and Internet Explorer I get the expected certificate error.
google-chrome ssl https ssl-certificate
asked Jan 30 at 14:16
user3657850user3657850
1
add a comment |
I have currently setup a website with a ssl cert which does not support wildcards and points to the bare domain. Upon testing the URL on different browsers I noticed that when requesting the domain with the www subdomain (https://www ... ), which is not supported by the certificate, gets a response in chrome. So I looked up the requested url in the dev tools and found that chrome does request the url without the www subdomain. Is this normal behavior for Chrome?
On other browsers this behavior is not occurring. In Firefox and Internet Explorer I get the expected certificate error.
google-chrome ssl https ssl-certificate
asked Jan 30 at 14:16
user3657850user3657850
1
I have currently setup a website with a ssl cert which does not support wildcards and points to the bare domain. Upon testing the URL on different browsers I noticed that when requesting the domain with the www subdomain (https://www ... ), which is not supported by the certificate, gets a response in chrome. So I looked up the requested url in the dev tools and found that chrome does request the url without the www subdomain. Is this normal behavior for Chrome?
On other browsers this behavior is not occurring. In Firefox and Internet Explorer I get the expected certificate error.
google-chrome ssl https ssl-certificate
google-chrome ssl https ssl-certificate
asked Jan 30 at 14:16
user3657850user3657850
1
asked Jan 30 at 14:16
user3657850user3657850
1
asked Jan 30 at 14:16
user3657850user3657850
1
asked Jan 30 at 14:16
user3657850user3657850
1
asked Jan 30 at 14:16
user3657850user3657850
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is most probably not a problem with the certificate, but a Chrome "feature".
If you set Chrome to look at
the flag chrome://flags/#omnibox-ui-hide-steady-state-url-trivial-subdomains,
you will see this text:
Omnibox UI Hide Steady-State URL Trivial Subdomains
In the omnibox, hide trivial subdomains from steady state displayed
URLs. Hidden portions are restored during editing. For Mac, this flag
will have no effect unless MacViews is enabled. – Mac, Windows, Linux,
Chrome OS, Android
Chrome considers "www" to be a "trivial subdomain", so hides it by default.
I don't have you website for testing, but disabling this flag might make
Chrome avoid adding the "www." before the website name.
If it is not enough, then Chrome is just overdoing its friendliness.
answered Jan 30 at 15:49
harrymcharrymc
259k14271573
This is not the case since Chrome does request the url without the subdomain. If Chrome would request the subdomain an error should occure because the certificate is not valid for the subdomain.
– user3657850
Jan 31 at 18:47
The friendly Chrome tries several trivial subdomains such as www, with or without, until one works. Many browsers have some such optimizations.
– harrymc
Jan 31 at 20:21
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400099%2fchrome-dropping-www-subdomain-on-request%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is most probably not a problem with the certificate, but a Chrome "feature".
If you set Chrome to look at
the flag chrome://flags/#omnibox-ui-hide-steady-state-url-trivial-subdomains,
you will see this text:
Omnibox UI Hide Steady-State URL Trivial Subdomains
In the omnibox, hide trivial subdomains from steady state displayed
URLs. Hidden portions are restored during editing. For Mac, this flag
will have no effect unless MacViews is enabled. – Mac, Windows, Linux,
Chrome OS, Android
Chrome considers "www" to be a "trivial subdomain", so hides it by default.
I don't have you website for testing, but disabling this flag might make
Chrome avoid adding the "www." before the website name.
If it is not enough, then Chrome is just overdoing its friendliness.
answered Jan 30 at 15:49
harrymcharrymc
259k14271573
This is not the case since Chrome does request the url without the subdomain. If Chrome would request the subdomain an error should occure because the certificate is not valid for the subdomain.
– user3657850
Jan 31 at 18:47
The friendly Chrome tries several trivial subdomains such as www, with or without, until one works. Many browsers have some such optimizations.
– harrymc
Jan 31 at 20:21
add a comment |
This is most probably not a problem with the certificate, but a Chrome "feature".
If you set Chrome to look at
the flag chrome://flags/#omnibox-ui-hide-steady-state-url-trivial-subdomains,
you will see this text:
Omnibox UI Hide Steady-State URL Trivial Subdomains
In the omnibox, hide trivial subdomains from steady state displayed
URLs. Hidden portions are restored during editing. For Mac, this flag
will have no effect unless MacViews is enabled. – Mac, Windows, Linux,
Chrome OS, Android
Chrome considers "www" to be a "trivial subdomain", so hides it by default.
I don't have you website for testing, but disabling this flag might make
Chrome avoid adding the "www." before the website name.
If it is not enough, then Chrome is just overdoing its friendliness.
answered Jan 30 at 15:49
harrymcharrymc
259k14271573
This is not the case since Chrome does request the url without the subdomain. If Chrome would request the subdomain an error should occure because the certificate is not valid for the subdomain.
– user3657850
Jan 31 at 18:47
The friendly Chrome tries several trivial subdomains such as www, with or without, until one works. Many browsers have some such optimizations.
– harrymc
Jan 31 at 20:21
add a comment |
This is most probably not a problem with the certificate, but a Chrome "feature".
If you set Chrome to look at
the flag chrome://flags/#omnibox-ui-hide-steady-state-url-trivial-subdomains,
you will see this text:
Omnibox UI Hide Steady-State URL Trivial Subdomains
In the omnibox, hide trivial subdomains from steady state displayed
URLs. Hidden portions are restored during editing. For Mac, this flag
will have no effect unless MacViews is enabled. – Mac, Windows, Linux,
Chrome OS, Android
Chrome considers "www" to be a "trivial subdomain", so hides it by default.
I don't have you website for testing, but disabling this flag might make
Chrome avoid adding the "www." before the website name.
If it is not enough, then Chrome is just overdoing its friendliness.
answered Jan 30 at 15:49
harrymcharrymc
259k14271573
This is most probably not a problem with the certificate, but a Chrome "feature".
If you set Chrome to look at
the flag chrome://flags/#omnibox-ui-hide-steady-state-url-trivial-subdomains,
you will see this text:
Omnibox UI Hide Steady-State URL Trivial Subdomains
In the omnibox, hide trivial subdomains from steady state displayed
URLs. Hidden portions are restored during editing. For Mac, this flag
will have no effect unless MacViews is enabled. – Mac, Windows, Linux,
Chrome OS, Android
Chrome considers "www" to be a "trivial subdomain", so hides it by default.
I don't have you website for testing, but disabling this flag might make
Chrome avoid adding the "www." before the website name.
If it is not enough, then Chrome is just overdoing its friendliness.
answered Jan 30 at 15:49
harrymcharrymc
259k14271573
answered Jan 30 at 15:49
harrymcharrymc
259k14271573
answered Jan 30 at 15:49
harrymcharrymc
259k14271573
answered Jan 30 at 15:49
harrymcharrymc
259k14271573
259k14271573
This is not the case since Chrome does request the url without the subdomain. If Chrome would request the subdomain an error should occure because the certificate is not valid for the subdomain.
– user3657850
Jan 31 at 18:47
The friendly Chrome tries several trivial subdomains such as www, with or without, until one works. Many browsers have some such optimizations.
– harrymc
Jan 31 at 20:21
add a comment |
This is not the case since Chrome does request the url without the subdomain. If Chrome would request the subdomain an error should occure because the certificate is not valid for the subdomain.
– user3657850
Jan 31 at 18:47
The friendly Chrome tries several trivial subdomains such as www, with or without, until one works. Many browsers have some such optimizations.
– harrymc
Jan 31 at 20:21
This is not the case since Chrome does request the url without the subdomain. If Chrome would request the subdomain an error should occure because the certificate is not valid for the subdomain.
– user3657850
Jan 31 at 18:47
This is not the case since Chrome does request the url without the subdomain. If Chrome would request the subdomain an error should occure because the certificate is not valid for the subdomain.
– user3657850
Jan 31 at 18:47
The friendly Chrome tries several trivial subdomains such as www, with or without, until one works. Many browsers have some such optimizations.
– harrymc
Jan 31 at 20:21
The friendly Chrome tries several trivial subdomains such as www, with or without, until one works. Many browsers have some such optimizations.
– harrymc
Jan 31 at 20:21
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400099%2fchrome-dropping-www-subdomain-on-request%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
