Problems When redirecting page with angularjs in IE9
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have the following script to redirect to the page I want
$location.$$urlUpdatedByLocation = true;
$location.$$absUrl = location.origin+location.pathname+"busqTerceros.html";
In the file busqTerceros.html I have the following:
<meta http-equiv="refresh" content="0; url=/cones/#!/search" />
This search is done from the AngularJS api router.
from what I've read in forums somehow IE loses the route when using #!
Does anyone know why IE does this? How can it be solved?
This works in Google chrome, Firefox, but not in IE, the error that was generated on the screen was the following:
Error
javascript angularjs internet-explorer
add a comment |
I have the following script to redirect to the page I want
$location.$$urlUpdatedByLocation = true;
$location.$$absUrl = location.origin+location.pathname+"busqTerceros.html";
In the file busqTerceros.html I have the following:
<meta http-equiv="refresh" content="0; url=/cones/#!/search" />
This search is done from the AngularJS api router.
from what I've read in forums somehow IE loses the route when using #!
Does anyone know why IE does this? How can it be solved?
This works in Google chrome, Firefox, but not in IE, the error that was generated on the screen was the following:
Error
javascript angularjs internet-explorer
I don't understand what you're trying to do. You're redirecting to a page that will immediately redirect you back to a different url? Why not load that url directly instead of taking a detour with the meta refresh. Also, if you're using angular, why not use the angular router to do all the redirecting? So could you please explain what you're trying to achieve?
– Shilly
Nov 16 '18 at 15:11
I am solving an issue of a system which was already working with this logic, but the problem of working with this logic is that in IE this redirect is not working, the idea is to try to solve the problem with the logic that already exists and if there is no solution I will have to do all this from the router.
– F.Lopez
Nov 16 '18 at 15:19
I haven't seen a<meta>
refresh since the 90's, so the app might be in need of a rewrite anyway. :) Have you tried relative paths? Or replacing the entire logic withwindow.location.href
manipulation? Or serverside redirections?
– Shilly
Nov 16 '18 at 15:24
try the redirection window.location.href and others derived from JS but the result is always the same an infinite loop.
– F.Lopez
Nov 16 '18 at 15:38
I'm afraid I'll have to use the angular router to make this work.
– F.Lopez
Nov 16 '18 at 15:41
add a comment |
I have the following script to redirect to the page I want
$location.$$urlUpdatedByLocation = true;
$location.$$absUrl = location.origin+location.pathname+"busqTerceros.html";
In the file busqTerceros.html I have the following:
<meta http-equiv="refresh" content="0; url=/cones/#!/search" />
This search is done from the AngularJS api router.
from what I've read in forums somehow IE loses the route when using #!
Does anyone know why IE does this? How can it be solved?
This works in Google chrome, Firefox, but not in IE, the error that was generated on the screen was the following:
Error
javascript angularjs internet-explorer
I have the following script to redirect to the page I want
$location.$$urlUpdatedByLocation = true;
$location.$$absUrl = location.origin+location.pathname+"busqTerceros.html";
In the file busqTerceros.html I have the following:
<meta http-equiv="refresh" content="0; url=/cones/#!/search" />
This search is done from the AngularJS api router.
from what I've read in forums somehow IE loses the route when using #!
Does anyone know why IE does this? How can it be solved?
This works in Google chrome, Firefox, but not in IE, the error that was generated on the screen was the following:
Error
javascript angularjs internet-explorer
javascript angularjs internet-explorer
edited Nov 19 '18 at 23:08
F.Lopez
asked Nov 16 '18 at 15:04
F.LopezF.Lopez
10115
10115
I don't understand what you're trying to do. You're redirecting to a page that will immediately redirect you back to a different url? Why not load that url directly instead of taking a detour with the meta refresh. Also, if you're using angular, why not use the angular router to do all the redirecting? So could you please explain what you're trying to achieve?
– Shilly
Nov 16 '18 at 15:11
I am solving an issue of a system which was already working with this logic, but the problem of working with this logic is that in IE this redirect is not working, the idea is to try to solve the problem with the logic that already exists and if there is no solution I will have to do all this from the router.
– F.Lopez
Nov 16 '18 at 15:19
I haven't seen a<meta>
refresh since the 90's, so the app might be in need of a rewrite anyway. :) Have you tried relative paths? Or replacing the entire logic withwindow.location.href
manipulation? Or serverside redirections?
– Shilly
Nov 16 '18 at 15:24
try the redirection window.location.href and others derived from JS but the result is always the same an infinite loop.
– F.Lopez
Nov 16 '18 at 15:38
I'm afraid I'll have to use the angular router to make this work.
– F.Lopez
Nov 16 '18 at 15:41
add a comment |
I don't understand what you're trying to do. You're redirecting to a page that will immediately redirect you back to a different url? Why not load that url directly instead of taking a detour with the meta refresh. Also, if you're using angular, why not use the angular router to do all the redirecting? So could you please explain what you're trying to achieve?
– Shilly
Nov 16 '18 at 15:11
I am solving an issue of a system which was already working with this logic, but the problem of working with this logic is that in IE this redirect is not working, the idea is to try to solve the problem with the logic that already exists and if there is no solution I will have to do all this from the router.
– F.Lopez
Nov 16 '18 at 15:19
I haven't seen a<meta>
refresh since the 90's, so the app might be in need of a rewrite anyway. :) Have you tried relative paths? Or replacing the entire logic withwindow.location.href
manipulation? Or serverside redirections?
– Shilly
Nov 16 '18 at 15:24
try the redirection window.location.href and others derived from JS but the result is always the same an infinite loop.
– F.Lopez
Nov 16 '18 at 15:38
I'm afraid I'll have to use the angular router to make this work.
– F.Lopez
Nov 16 '18 at 15:41
I don't understand what you're trying to do. You're redirecting to a page that will immediately redirect you back to a different url? Why not load that url directly instead of taking a detour with the meta refresh. Also, if you're using angular, why not use the angular router to do all the redirecting? So could you please explain what you're trying to achieve?
– Shilly
Nov 16 '18 at 15:11
I don't understand what you're trying to do. You're redirecting to a page that will immediately redirect you back to a different url? Why not load that url directly instead of taking a detour with the meta refresh. Also, if you're using angular, why not use the angular router to do all the redirecting? So could you please explain what you're trying to achieve?
– Shilly
Nov 16 '18 at 15:11
I am solving an issue of a system which was already working with this logic, but the problem of working with this logic is that in IE this redirect is not working, the idea is to try to solve the problem with the logic that already exists and if there is no solution I will have to do all this from the router.
– F.Lopez
Nov 16 '18 at 15:19
I am solving an issue of a system which was already working with this logic, but the problem of working with this logic is that in IE this redirect is not working, the idea is to try to solve the problem with the logic that already exists and if there is no solution I will have to do all this from the router.
– F.Lopez
Nov 16 '18 at 15:19
I haven't seen a
<meta>
refresh since the 90's, so the app might be in need of a rewrite anyway. :) Have you tried relative paths? Or replacing the entire logic with window.location.href
manipulation? Or serverside redirections?– Shilly
Nov 16 '18 at 15:24
I haven't seen a
<meta>
refresh since the 90's, so the app might be in need of a rewrite anyway. :) Have you tried relative paths? Or replacing the entire logic with window.location.href
manipulation? Or serverside redirections?– Shilly
Nov 16 '18 at 15:24
try the redirection window.location.href and others derived from JS but the result is always the same an infinite loop.
– F.Lopez
Nov 16 '18 at 15:38
try the redirection window.location.href and others derived from JS but the result is always the same an infinite loop.
– F.Lopez
Nov 16 '18 at 15:38
I'm afraid I'll have to use the angular router to make this work.
– F.Lopez
Nov 16 '18 at 15:41
I'm afraid I'll have to use the angular router to make this work.
– F.Lopez
Nov 16 '18 at 15:41
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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%2fstackoverflow.com%2fquestions%2f53340387%2fproblems-when-redirecting-page-with-angularjs-in-ie9%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53340387%2fproblems-when-redirecting-page-with-angularjs-in-ie9%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
I don't understand what you're trying to do. You're redirecting to a page that will immediately redirect you back to a different url? Why not load that url directly instead of taking a detour with the meta refresh. Also, if you're using angular, why not use the angular router to do all the redirecting? So could you please explain what you're trying to achieve?
– Shilly
Nov 16 '18 at 15:11
I am solving an issue of a system which was already working with this logic, but the problem of working with this logic is that in IE this redirect is not working, the idea is to try to solve the problem with the logic that already exists and if there is no solution I will have to do all this from the router.
– F.Lopez
Nov 16 '18 at 15:19
I haven't seen a
<meta>
refresh since the 90's, so the app might be in need of a rewrite anyway. :) Have you tried relative paths? Or replacing the entire logic withwindow.location.href
manipulation? Or serverside redirections?– Shilly
Nov 16 '18 at 15:24
try the redirection window.location.href and others derived from JS but the result is always the same an infinite loop.
– F.Lopez
Nov 16 '18 at 15:38
I'm afraid I'll have to use the angular router to make this work.
– F.Lopez
Nov 16 '18 at 15:41