How can I get Google Chrome to go to an internal page without performing an external search?
I am trying to replicate some behavior that I have seen in Internet Explorer version 11 in Google Chrome version 71.
Whenever I search myalias/someinternalpage
I am brought to the internal page.
When I search the same thing in Google Chrome's Omnibar I am taken to an external search, and at the top I am given a message, with a link, that reads
Did you mean to go to http://myalias/someinternalpage?
When I click on this link I will be taken to the page, and Chrome will start recognizing the alias.
This is inconvenient. How can I get Chrome to have the same behavior as Internet Explorer?
google-chrome dns alias
add a comment |
I am trying to replicate some behavior that I have seen in Internet Explorer version 11 in Google Chrome version 71.
Whenever I search myalias/someinternalpage
I am brought to the internal page.
When I search the same thing in Google Chrome's Omnibar I am taken to an external search, and at the top I am given a message, with a link, that reads
Did you mean to go to http://myalias/someinternalpage?
When I click on this link I will be taken to the page, and Chrome will start recognizing the alias.
This is inconvenient. How can I get Chrome to have the same behavior as Internet Explorer?
google-chrome dns alias
Some people report that adding a trailing slash will cause Chrome to treat it as a URL, and not as a search term. That is, trymyalias/someinternalpage/
.
– Doug Deden
Jan 24 at 23:13
add a comment |
I am trying to replicate some behavior that I have seen in Internet Explorer version 11 in Google Chrome version 71.
Whenever I search myalias/someinternalpage
I am brought to the internal page.
When I search the same thing in Google Chrome's Omnibar I am taken to an external search, and at the top I am given a message, with a link, that reads
Did you mean to go to http://myalias/someinternalpage?
When I click on this link I will be taken to the page, and Chrome will start recognizing the alias.
This is inconvenient. How can I get Chrome to have the same behavior as Internet Explorer?
google-chrome dns alias
I am trying to replicate some behavior that I have seen in Internet Explorer version 11 in Google Chrome version 71.
Whenever I search myalias/someinternalpage
I am brought to the internal page.
When I search the same thing in Google Chrome's Omnibar I am taken to an external search, and at the top I am given a message, with a link, that reads
Did you mean to go to http://myalias/someinternalpage?
When I click on this link I will be taken to the page, and Chrome will start recognizing the alias.
This is inconvenient. How can I get Chrome to have the same behavior as Internet Explorer?
google-chrome dns alias
google-chrome dns alias
edited Jan 25 at 1:02
fixer1234
18.9k144982
18.9k144982
asked Jan 24 at 21:46
BradleyGamiMarquesBradleyGamiMarques
11
11
Some people report that adding a trailing slash will cause Chrome to treat it as a URL, and not as a search term. That is, trymyalias/someinternalpage/
.
– Doug Deden
Jan 24 at 23:13
add a comment |
Some people report that adding a trailing slash will cause Chrome to treat it as a URL, and not as a search term. That is, trymyalias/someinternalpage/
.
– Doug Deden
Jan 24 at 23:13
Some people report that adding a trailing slash will cause Chrome to treat it as a URL, and not as a search term. That is, try
myalias/someinternalpage/
.– Doug Deden
Jan 24 at 23:13
Some people report that adding a trailing slash will cause Chrome to treat it as a URL, and not as a search term. That is, try
myalias/someinternalpage/
.– Doug Deden
Jan 24 at 23:13
add a comment |
1 Answer
1
active
oldest
votes
From this Chromium.org discussion, you have a few options.
There are a few solutions, but none of them is equivalent to IE's config switch (hence the presence of this bug).
(1) Enterprise policy can disable search entirely, so the Chrome address bar never searches. This also prevents searching for less ambiguous inputs, though.
(2) Users can clue Chrome in that a never-seen-before hostname is a hostname by e.g. appending a "/" to the end (or prepending a scheme, but that's more annoying to type).
(3) The designed way Chrome is intended to work in this case is that when a user inputs something that is a potential intranet hostname, Chrome does a background HTTP HEAD request to that hostname, and if it gets a valid reply, it displays an infobar atop the search result page, asking "Did you mean to go to http:///?" If a user clicks that link, not only does it navigate to this hostname now, it also remembers that hostname in the future to avoid searching again. Similarly, doing any other successful typed navigation to that host (e.g. "hostname/" as suggested in (2)) will also cause Chrome to never search for that host again.
Is there a way to configure Chrome to already knowmyalias
? That way when Chrome is distributed to enterprise machines, users can resolve the internal web pages without the need to type a scheme or needing to typemyalias/
and then continuing on with their day by typingmyalias/someinternalpage
. If that doesn't make sense please let me know.
– BradleyGamiMarques
Jan 25 at 16:16
Another suggestion would be to write a Chrome extension that checks searches in the Omnibar, and if it findsmyalias
it prepends the scheme and then lets Chrome handle it from there.
– BradleyGamiMarques
Jan 25 at 17:43
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%2f1398098%2fhow-can-i-get-google-chrome-to-go-to-an-internal-page-without-performing-an-exte%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
From this Chromium.org discussion, you have a few options.
There are a few solutions, but none of them is equivalent to IE's config switch (hence the presence of this bug).
(1) Enterprise policy can disable search entirely, so the Chrome address bar never searches. This also prevents searching for less ambiguous inputs, though.
(2) Users can clue Chrome in that a never-seen-before hostname is a hostname by e.g. appending a "/" to the end (or prepending a scheme, but that's more annoying to type).
(3) The designed way Chrome is intended to work in this case is that when a user inputs something that is a potential intranet hostname, Chrome does a background HTTP HEAD request to that hostname, and if it gets a valid reply, it displays an infobar atop the search result page, asking "Did you mean to go to http:///?" If a user clicks that link, not only does it navigate to this hostname now, it also remembers that hostname in the future to avoid searching again. Similarly, doing any other successful typed navigation to that host (e.g. "hostname/" as suggested in (2)) will also cause Chrome to never search for that host again.
Is there a way to configure Chrome to already knowmyalias
? That way when Chrome is distributed to enterprise machines, users can resolve the internal web pages without the need to type a scheme or needing to typemyalias/
and then continuing on with their day by typingmyalias/someinternalpage
. If that doesn't make sense please let me know.
– BradleyGamiMarques
Jan 25 at 16:16
Another suggestion would be to write a Chrome extension that checks searches in the Omnibar, and if it findsmyalias
it prepends the scheme and then lets Chrome handle it from there.
– BradleyGamiMarques
Jan 25 at 17:43
add a comment |
From this Chromium.org discussion, you have a few options.
There are a few solutions, but none of them is equivalent to IE's config switch (hence the presence of this bug).
(1) Enterprise policy can disable search entirely, so the Chrome address bar never searches. This also prevents searching for less ambiguous inputs, though.
(2) Users can clue Chrome in that a never-seen-before hostname is a hostname by e.g. appending a "/" to the end (or prepending a scheme, but that's more annoying to type).
(3) The designed way Chrome is intended to work in this case is that when a user inputs something that is a potential intranet hostname, Chrome does a background HTTP HEAD request to that hostname, and if it gets a valid reply, it displays an infobar atop the search result page, asking "Did you mean to go to http:///?" If a user clicks that link, not only does it navigate to this hostname now, it also remembers that hostname in the future to avoid searching again. Similarly, doing any other successful typed navigation to that host (e.g. "hostname/" as suggested in (2)) will also cause Chrome to never search for that host again.
Is there a way to configure Chrome to already knowmyalias
? That way when Chrome is distributed to enterprise machines, users can resolve the internal web pages without the need to type a scheme or needing to typemyalias/
and then continuing on with their day by typingmyalias/someinternalpage
. If that doesn't make sense please let me know.
– BradleyGamiMarques
Jan 25 at 16:16
Another suggestion would be to write a Chrome extension that checks searches in the Omnibar, and if it findsmyalias
it prepends the scheme and then lets Chrome handle it from there.
– BradleyGamiMarques
Jan 25 at 17:43
add a comment |
From this Chromium.org discussion, you have a few options.
There are a few solutions, but none of them is equivalent to IE's config switch (hence the presence of this bug).
(1) Enterprise policy can disable search entirely, so the Chrome address bar never searches. This also prevents searching for less ambiguous inputs, though.
(2) Users can clue Chrome in that a never-seen-before hostname is a hostname by e.g. appending a "/" to the end (or prepending a scheme, but that's more annoying to type).
(3) The designed way Chrome is intended to work in this case is that when a user inputs something that is a potential intranet hostname, Chrome does a background HTTP HEAD request to that hostname, and if it gets a valid reply, it displays an infobar atop the search result page, asking "Did you mean to go to http:///?" If a user clicks that link, not only does it navigate to this hostname now, it also remembers that hostname in the future to avoid searching again. Similarly, doing any other successful typed navigation to that host (e.g. "hostname/" as suggested in (2)) will also cause Chrome to never search for that host again.
From this Chromium.org discussion, you have a few options.
There are a few solutions, but none of them is equivalent to IE's config switch (hence the presence of this bug).
(1) Enterprise policy can disable search entirely, so the Chrome address bar never searches. This also prevents searching for less ambiguous inputs, though.
(2) Users can clue Chrome in that a never-seen-before hostname is a hostname by e.g. appending a "/" to the end (or prepending a scheme, but that's more annoying to type).
(3) The designed way Chrome is intended to work in this case is that when a user inputs something that is a potential intranet hostname, Chrome does a background HTTP HEAD request to that hostname, and if it gets a valid reply, it displays an infobar atop the search result page, asking "Did you mean to go to http:///?" If a user clicks that link, not only does it navigate to this hostname now, it also remembers that hostname in the future to avoid searching again. Similarly, doing any other successful typed navigation to that host (e.g. "hostname/" as suggested in (2)) will also cause Chrome to never search for that host again.
answered Jan 24 at 23:36
Doug DedenDoug Deden
860213
860213
Is there a way to configure Chrome to already knowmyalias
? That way when Chrome is distributed to enterprise machines, users can resolve the internal web pages without the need to type a scheme or needing to typemyalias/
and then continuing on with their day by typingmyalias/someinternalpage
. If that doesn't make sense please let me know.
– BradleyGamiMarques
Jan 25 at 16:16
Another suggestion would be to write a Chrome extension that checks searches in the Omnibar, and if it findsmyalias
it prepends the scheme and then lets Chrome handle it from there.
– BradleyGamiMarques
Jan 25 at 17:43
add a comment |
Is there a way to configure Chrome to already knowmyalias
? That way when Chrome is distributed to enterprise machines, users can resolve the internal web pages without the need to type a scheme or needing to typemyalias/
and then continuing on with their day by typingmyalias/someinternalpage
. If that doesn't make sense please let me know.
– BradleyGamiMarques
Jan 25 at 16:16
Another suggestion would be to write a Chrome extension that checks searches in the Omnibar, and if it findsmyalias
it prepends the scheme and then lets Chrome handle it from there.
– BradleyGamiMarques
Jan 25 at 17:43
Is there a way to configure Chrome to already know
myalias
? That way when Chrome is distributed to enterprise machines, users can resolve the internal web pages without the need to type a scheme or needing to type myalias/
and then continuing on with their day by typing myalias/someinternalpage
. If that doesn't make sense please let me know.– BradleyGamiMarques
Jan 25 at 16:16
Is there a way to configure Chrome to already know
myalias
? That way when Chrome is distributed to enterprise machines, users can resolve the internal web pages without the need to type a scheme or needing to type myalias/
and then continuing on with their day by typing myalias/someinternalpage
. If that doesn't make sense please let me know.– BradleyGamiMarques
Jan 25 at 16:16
Another suggestion would be to write a Chrome extension that checks searches in the Omnibar, and if it finds
myalias
it prepends the scheme and then lets Chrome handle it from there.– BradleyGamiMarques
Jan 25 at 17:43
Another suggestion would be to write a Chrome extension that checks searches in the Omnibar, and if it finds
myalias
it prepends the scheme and then lets Chrome handle it from there.– BradleyGamiMarques
Jan 25 at 17:43
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%2f1398098%2fhow-can-i-get-google-chrome-to-go-to-an-internal-page-without-performing-an-exte%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
Some people report that adding a trailing slash will cause Chrome to treat it as a URL, and not as a search term. That is, try
myalias/someinternalpage/
.– Doug Deden
Jan 24 at 23:13