Serverless computing in Azure with .NET

Configuring CORS

When you configure a web or mobile client-side scripts such as JavaScript to execute HTTP requests against a back-end service (such as an HTTP-triggered function), you often run into same origin restrictions. Most user agents (browsers or mobile browsers) apply same-origin restrictions to client-side scripts. Same-origin is defined as having the same hostname, protocol, and port as the code which originated the request. The same-origin policy is applied for security reasons to prevent the execution of malicious scripts, for instance, scripts trying to gain access to the user's sensitive data by using session cookies from the previous sessions which were stored by the browser. To read more about the same-origin policy, please ...