What is the issue CORS is trying to solve?
Solution 1:
The default behavior of web browsers that initiate requests from a page via JavaScript (AKA AJAX) is that they follow the same-origin policy. This means that requests can only be made via AJAX to the same domain (or sub domain). Requests to an entirely different domain will fail.
This restriction exists because requests made at other domains by your browser would carry along your cookies which often means you'd be logged in to the other site. So, without same-origin, any site could host JavaScript that called logout on stackoverflow.com for example, and it would log you out. Now imagine the complications when we talk about social networks, banking sites, etc.
So, all browsers simply restrict script-based network calls to their own domain to make it simple and safe.
Site X at www.x.com cannot make AJAX requests to site Y at www.y.com, only to *.x.com
There are some known work-arounds in place (such as JSONP which doesn't include cookies in the request), but these are not a permanent solution.
CORS allows these cross-domain requests to happen, but only when each side opts into CORS support.
Solution 2:
First, let's talk about the same origin policy. I'll quote from a previous answer of mine:
The same-origin policy was invented because it prevents code from one website from accessing credential-restricted content on another site. Ajax requests are by default sent with any auth cookies granted by the target site.
For example, suppose I accidentally load
http://evil.com/
, which sends a request forhttp://mail.google.com/
. If the SOP were not in place, and I was signed into Gmail, the script atevil.com
could see my inbox. If the site atevil.com
wants to loadmail.google.com
without my cookies, it can just use a proxy server; the public contents ofmail.google.com
are not a secret (but the contents ofmail.google.com
when accessed with my cookies are a secret).
(Note that I've said "credential-restricted content", but it can also be topology-restricted content when a website is only visible to certain IP addresses.)
Sometimes, however, it's not evil.com
trying to peek into your inbox. Sometimes, it's just a helpful website (say, http://goodsite.foo
) trying to use a public API from another origin (say, http://api.example.com
). The programmers who worked hard on api.example.com
want all origins to access their site's contents freely. In that case, the API server at api.example.com
can use CORS headers to allow goodsite.foo
(or any other requesting origin) to access its API responses.
So, in sum, we assume by default that cross-origin access is a bad thing (think of someone trying to read your inbox), but there are cases where it's a good thing (think of a website trying to access a public API). CORS allows the good case to happen when the requested site wants it to happen.