AnsweredAssumed Answered

Request Header not present in Access-Control-Allow-Headers List

Question asked by mrutherford on Oct 5, 2018
Latest reply on Oct 22, 2018 by Dustin Dauncey

I'm currently running into issues with the CORS assertion and IE 11. I've verified that this RestAPI endpoint is working without any issues in Chrome and Microsoft Edge.

 

I've configured the CORS assertion with the following settings and I always receive an error message in the IE developer console stating:

Viewing the Network tab I can see that the initial Preflight request is being made using the HTTP OPTIONS method with the Access-Control-Allow-Headers value in the Request and Response both containing the api-key header. 

 

Has anyone else ran into this issue and found a way around it? 

 

My settings in the CORS assertion are as follows: 

Outcomes