security restrictions on your browser’s security policy prevent your web browser from making ajax requests to a server in another domain. this is also known as same-origin policy. in other words, it is a known fact that browser security prevents a web page of one domain from executing ajax calls on another domain.here's where cors (cross-origin resource sharing) comes to the rescue. cors is a w3c standard that allows you to get away from the same origin policy adopted by the browsers to restrict access from one domain to resources belonging to another domain. you can enable cors for your web api using the respective web api package (depending on the version of web api in use) or owin middleware.note that an origin of a request comprises of: scheme, host and port number. so, two requests are considered to be from the same origin if they have the same scheme, host and port number. if any of these differ, the requests are considered to be cross origin, i.e., not belonging to identical ...