Unable to catch the success response IE
I have an application wherein it should work both in chrome and IE. API call using resource(ngResource) is working fine in chrome/Firefor - able to get response in success block when api is success. But in IE11 same api is going into error block. Please let me know if any configuration is required in resource factory.
angularjs api internet-explorer ngresource angularjs-ng-resource
add a comment |
I have an application wherein it should work both in chrome and IE. API call using resource(ngResource) is working fine in chrome/Firefor - able to get response in success block when api is success. But in IE11 same api is going into error block. Please let me know if any configuration is required in resource factory.
angularjs api internet-explorer ngresource angularjs-ng-resource
Can you post the Enough code to reproduce the problem as in Minimal, Complete, and Verifiable example. I test this sample on my side in IE 11, it seems that everything works well. Besides, I suggest you could use F12 developer tools to check whether it display some error.
– Zhi Lv - MSFT
Nov 26 '18 at 2:17
ResourceService.js var Resource = $resource(routeUrl +/records
, {}, { update: ResourceFactory.prepareDefaultResource({ method: 'POST', url: routeUrl +/update
, isArray: false, cache: false, }), }); return Resource; controller this.provider = ResourceService; this.provider.update(params, (response) => { console.log("success block"); }, (error) => { console.log("error block"); });
– Akash Pattem
Nov 27 '18 at 7:07
add a comment |
I have an application wherein it should work both in chrome and IE. API call using resource(ngResource) is working fine in chrome/Firefor - able to get response in success block when api is success. But in IE11 same api is going into error block. Please let me know if any configuration is required in resource factory.
angularjs api internet-explorer ngresource angularjs-ng-resource
I have an application wherein it should work both in chrome and IE. API call using resource(ngResource) is working fine in chrome/Firefor - able to get response in success block when api is success. But in IE11 same api is going into error block. Please let me know if any configuration is required in resource factory.
angularjs api internet-explorer ngresource angularjs-ng-resource
angularjs api internet-explorer ngresource angularjs-ng-resource
asked Nov 23 '18 at 6:59
Akash Pattem
2317
2317
Can you post the Enough code to reproduce the problem as in Minimal, Complete, and Verifiable example. I test this sample on my side in IE 11, it seems that everything works well. Besides, I suggest you could use F12 developer tools to check whether it display some error.
– Zhi Lv - MSFT
Nov 26 '18 at 2:17
ResourceService.js var Resource = $resource(routeUrl +/records
, {}, { update: ResourceFactory.prepareDefaultResource({ method: 'POST', url: routeUrl +/update
, isArray: false, cache: false, }), }); return Resource; controller this.provider = ResourceService; this.provider.update(params, (response) => { console.log("success block"); }, (error) => { console.log("error block"); });
– Akash Pattem
Nov 27 '18 at 7:07
add a comment |
Can you post the Enough code to reproduce the problem as in Minimal, Complete, and Verifiable example. I test this sample on my side in IE 11, it seems that everything works well. Besides, I suggest you could use F12 developer tools to check whether it display some error.
– Zhi Lv - MSFT
Nov 26 '18 at 2:17
ResourceService.js var Resource = $resource(routeUrl +/records
, {}, { update: ResourceFactory.prepareDefaultResource({ method: 'POST', url: routeUrl +/update
, isArray: false, cache: false, }), }); return Resource; controller this.provider = ResourceService; this.provider.update(params, (response) => { console.log("success block"); }, (error) => { console.log("error block"); });
– Akash Pattem
Nov 27 '18 at 7:07
Can you post the Enough code to reproduce the problem as in Minimal, Complete, and Verifiable example. I test this sample on my side in IE 11, it seems that everything works well. Besides, I suggest you could use F12 developer tools to check whether it display some error.
– Zhi Lv - MSFT
Nov 26 '18 at 2:17
Can you post the Enough code to reproduce the problem as in Minimal, Complete, and Verifiable example. I test this sample on my side in IE 11, it seems that everything works well. Besides, I suggest you could use F12 developer tools to check whether it display some error.
– Zhi Lv - MSFT
Nov 26 '18 at 2:17
ResourceService.js var Resource = $resource(routeUrl +
/records
, {}, { update: ResourceFactory.prepareDefaultResource({ method: 'POST', url: routeUrl + /update
, isArray: false, cache: false, }), }); return Resource; controller this.provider = ResourceService; this.provider.update(params, (response) => { console.log("success block"); }, (error) => { console.log("error block"); });– Akash Pattem
Nov 27 '18 at 7:07
ResourceService.js var Resource = $resource(routeUrl +
/records
, {}, { update: ResourceFactory.prepareDefaultResource({ method: 'POST', url: routeUrl + /update
, isArray: false, cache: false, }), }); return Resource; controller this.provider = ResourceService; this.provider.update(params, (response) => { console.log("success block"); }, (error) => { console.log("error block"); });– Akash Pattem
Nov 27 '18 at 7:07
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%2f53441981%2funable-to-catch-the-success-response-ie%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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53441981%2funable-to-catch-the-success-response-ie%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
Can you post the Enough code to reproduce the problem as in Minimal, Complete, and Verifiable example. I test this sample on my side in IE 11, it seems that everything works well. Besides, I suggest you could use F12 developer tools to check whether it display some error.
– Zhi Lv - MSFT
Nov 26 '18 at 2:17
ResourceService.js var Resource = $resource(routeUrl +
/records
, {}, { update: ResourceFactory.prepareDefaultResource({ method: 'POST', url: routeUrl +/update
, isArray: false, cache: false, }), }); return Resource; controller this.provider = ResourceService; this.provider.update(params, (response) => { console.log("success block"); }, (error) => { console.log("error block"); });– Akash Pattem
Nov 27 '18 at 7:07