We recently migrated an API application from Azure Cloud Services to Azure Websites, and some clients are still using our legacy protocol for authentication, which uses cookies (instead of the usual Authorization: Bearer
HTTP header). We need to support this authentication protocol for a little longer as the clients will not be able to migrate right away.
To support cookies in a cross-origin ajax request directed to the API, the client needs to set the withCredentials
setting to true
in the XMLHttpRequest, and the server needs to repond with the Access-Control-Allow-Credentials
header as well to any CORS request.
The problem we face is that the Azure Website manages CORS all by itself, and uses its own configuration (which is limited to a list of allowed origins) for the response, which does not allow this header to be set... thus breaking the application for all our Ajax clients!
Is there a way to (temporarily) add this header in the responses?
We finally managed to understand the behavior of the Azure Apps CORS middleware. To disable it, you have to clear every single allowed origin entry in the CORS blade of your web app (including
*
). Then you can manage CORS by yourself, either using the Web Api 2 functionality or using the web.config.The information is even available in the documentation:
So the final answer is: If your application does not need a very specific CORS management, you can use Azure App Service CORS. Otherwise you will need to handle it yourself and disable all CORS configuration in the web app.
This is Something that you can do in the web.config file that is available in your web app.
You can edit it using Visual Studio Online (Monaco) which is a Tools that you add from the Azure Portal.
Read more here : http://enable-cors.org/server_iis7.html