I am getting and error in chrome as 400 bad request for preflight. Angular + Azure Functions











up vote
0
down vote

favorite












I am using Azure Functions to host apis and Angular as front end. I am facing issues with Chrome PreFlight [OPTIONS] request which gets 400 Bad request Error.



Screenshot of Request in Chome



It works on my Dev Machine. I do not see any pre flight errors.










share|improve this question




















  • 1




    Have you added the host where angular front end locates to CORS list?
    – Jerry Liu
    Nov 22 at 6:20










  • I added that and I added * in Cors but still fails..
    – user1387192
    Nov 22 at 7:25










  • On more digging I found that when I add Authorization bearer token in the header I get this error...
    – user1387192
    Nov 22 at 7:26










  • I added the entry and it worked....
    – user1387192
    Nov 22 at 7:37















up vote
0
down vote

favorite












I am using Azure Functions to host apis and Angular as front end. I am facing issues with Chrome PreFlight [OPTIONS] request which gets 400 Bad request Error.



Screenshot of Request in Chome



It works on my Dev Machine. I do not see any pre flight errors.










share|improve this question




















  • 1




    Have you added the host where angular front end locates to CORS list?
    – Jerry Liu
    Nov 22 at 6:20










  • I added that and I added * in Cors but still fails..
    – user1387192
    Nov 22 at 7:25










  • On more digging I found that when I add Authorization bearer token in the header I get this error...
    – user1387192
    Nov 22 at 7:26










  • I added the entry and it worked....
    – user1387192
    Nov 22 at 7:37













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am using Azure Functions to host apis and Angular as front end. I am facing issues with Chrome PreFlight [OPTIONS] request which gets 400 Bad request Error.



Screenshot of Request in Chome



It works on my Dev Machine. I do not see any pre flight errors.










share|improve this question















I am using Azure Functions to host apis and Angular as front end. I am facing issues with Chrome PreFlight [OPTIONS] request which gets 400 Bad request Error.



Screenshot of Request in Chome



It works on my Dev Machine. I do not see any pre flight errors.







angular azure azure-functions






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 at 6:22









Jerry Liu

7,5181427




7,5181427










asked Nov 22 at 5:44









user1387192

51




51








  • 1




    Have you added the host where angular front end locates to CORS list?
    – Jerry Liu
    Nov 22 at 6:20










  • I added that and I added * in Cors but still fails..
    – user1387192
    Nov 22 at 7:25










  • On more digging I found that when I add Authorization bearer token in the header I get this error...
    – user1387192
    Nov 22 at 7:26










  • I added the entry and it worked....
    – user1387192
    Nov 22 at 7:37














  • 1




    Have you added the host where angular front end locates to CORS list?
    – Jerry Liu
    Nov 22 at 6:20










  • I added that and I added * in Cors but still fails..
    – user1387192
    Nov 22 at 7:25










  • On more digging I found that when I add Authorization bearer token in the header I get this error...
    – user1387192
    Nov 22 at 7:26










  • I added the entry and it worked....
    – user1387192
    Nov 22 at 7:37








1




1




Have you added the host where angular front end locates to CORS list?
– Jerry Liu
Nov 22 at 6:20




Have you added the host where angular front end locates to CORS list?
– Jerry Liu
Nov 22 at 6:20












I added that and I added * in Cors but still fails..
– user1387192
Nov 22 at 7:25




I added that and I added * in Cors but still fails..
– user1387192
Nov 22 at 7:25












On more digging I found that when I add Authorization bearer token in the header I get this error...
– user1387192
Nov 22 at 7:26




On more digging I found that when I add Authorization bearer token in the header I get this error...
– user1387192
Nov 22 at 7:26












I added the entry and it worked....
– user1387192
Nov 22 at 7:37




I added the entry and it worked....
– user1387192
Nov 22 at 7:37












1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










You need to go to Platform Features tab -> Click on CORS and add your FrontEnd URL to the list of Allowed Origins.



enter image description here






share|improve this answer





















  • I tried that it did not work.. On more digging I found that when I add Authorization bearer token in the header I get this error...
    – user1387192
    Nov 22 at 7:27










  • If you add * to CORS list you have to remove all the other URLs. Otherwise neither of them are applicable
    – Naren
    Nov 22 at 7:30












  • Thanks man it worked.. I was adding / at the end of the url....
    – user1387192
    Nov 22 at 7:36










  • @user1387192 Please accept Naren's answer to close your question.
    – Jerry Liu
    Nov 22 at 7:39











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',
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53424566%2fi-am-getting-and-error-in-chrome-as-400-bad-request-for-preflight-angular-azu%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








up vote
0
down vote



accepted










You need to go to Platform Features tab -> Click on CORS and add your FrontEnd URL to the list of Allowed Origins.



enter image description here






share|improve this answer





















  • I tried that it did not work.. On more digging I found that when I add Authorization bearer token in the header I get this error...
    – user1387192
    Nov 22 at 7:27










  • If you add * to CORS list you have to remove all the other URLs. Otherwise neither of them are applicable
    – Naren
    Nov 22 at 7:30












  • Thanks man it worked.. I was adding / at the end of the url....
    – user1387192
    Nov 22 at 7:36










  • @user1387192 Please accept Naren's answer to close your question.
    – Jerry Liu
    Nov 22 at 7:39















up vote
0
down vote



accepted










You need to go to Platform Features tab -> Click on CORS and add your FrontEnd URL to the list of Allowed Origins.



enter image description here






share|improve this answer





















  • I tried that it did not work.. On more digging I found that when I add Authorization bearer token in the header I get this error...
    – user1387192
    Nov 22 at 7:27










  • If you add * to CORS list you have to remove all the other URLs. Otherwise neither of them are applicable
    – Naren
    Nov 22 at 7:30












  • Thanks man it worked.. I was adding / at the end of the url....
    – user1387192
    Nov 22 at 7:36










  • @user1387192 Please accept Naren's answer to close your question.
    – Jerry Liu
    Nov 22 at 7:39













up vote
0
down vote



accepted







up vote
0
down vote



accepted






You need to go to Platform Features tab -> Click on CORS and add your FrontEnd URL to the list of Allowed Origins.



enter image description here






share|improve this answer












You need to go to Platform Features tab -> Click on CORS and add your FrontEnd URL to the list of Allowed Origins.



enter image description here







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 22 at 6:27









Naren

57426




57426












  • I tried that it did not work.. On more digging I found that when I add Authorization bearer token in the header I get this error...
    – user1387192
    Nov 22 at 7:27










  • If you add * to CORS list you have to remove all the other URLs. Otherwise neither of them are applicable
    – Naren
    Nov 22 at 7:30












  • Thanks man it worked.. I was adding / at the end of the url....
    – user1387192
    Nov 22 at 7:36










  • @user1387192 Please accept Naren's answer to close your question.
    – Jerry Liu
    Nov 22 at 7:39


















  • I tried that it did not work.. On more digging I found that when I add Authorization bearer token in the header I get this error...
    – user1387192
    Nov 22 at 7:27










  • If you add * to CORS list you have to remove all the other URLs. Otherwise neither of them are applicable
    – Naren
    Nov 22 at 7:30












  • Thanks man it worked.. I was adding / at the end of the url....
    – user1387192
    Nov 22 at 7:36










  • @user1387192 Please accept Naren's answer to close your question.
    – Jerry Liu
    Nov 22 at 7:39
















I tried that it did not work.. On more digging I found that when I add Authorization bearer token in the header I get this error...
– user1387192
Nov 22 at 7:27




I tried that it did not work.. On more digging I found that when I add Authorization bearer token in the header I get this error...
– user1387192
Nov 22 at 7:27












If you add * to CORS list you have to remove all the other URLs. Otherwise neither of them are applicable
– Naren
Nov 22 at 7:30






If you add * to CORS list you have to remove all the other URLs. Otherwise neither of them are applicable
– Naren
Nov 22 at 7:30














Thanks man it worked.. I was adding / at the end of the url....
– user1387192
Nov 22 at 7:36




Thanks man it worked.. I was adding / at the end of the url....
– user1387192
Nov 22 at 7:36












@user1387192 Please accept Naren's answer to close your question.
– Jerry Liu
Nov 22 at 7:39




@user1387192 Please accept Naren's answer to close your question.
– Jerry Liu
Nov 22 at 7:39


















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53424566%2fi-am-getting-and-error-in-chrome-as-400-bad-request-for-preflight-angular-azu%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Trompette piccolo

Slow SSRS Report in dynamic grouping and multiple parameters

Simon Yates (cyclisme)