Dealing with CORS
Tags: web, cors, security
Published: 2020-01-27 09:50:44

---
title: Dealing with CORS
published: true
description: CORS is hard to understand and has so many gotchas! Here is a play
tags: web, cors, security
cover_image: https://thepracticaldev.s3.amazonaws.com/i/f2zzd84k7wano45cqdl6.png
canonical_url: https://stegriff.co.uk/upblog/dealing-with-cors/
---

If you're a web developer, CORS is probably a recurring phantom that comes back every other project to steal a whole week. After my most recent wrestle with it, I wanted to write a playbook to the common scenarios, gotchas, and workarounds. I hope it helps you!

{% twitter 1116013041521504256 %}

Cross Origin Resource Sharing (CORS) is a security measure **enforced by web browsers** which affects calls made from a web browser to a remote resource like an API on another web domain.

The key to understanding CORS is to understand that it is the browser which is blocking, but to allow CORS, the server has to add special headers which satisfy the browser into allowing the connection. As such, CORS blocking doesn't affect back-end solutions that call APIs.


## 1. Simple requests

If you are just doing an HTTP GET, HEAD, or POST (with no custom/exotic HTTP headers and a "normal" content-type), then you're making a [simple request][simp].

![Simples](https://thepracticaldev.s3.amazonaws.com/i/nm6iyk9qars4no83c20x.jpg)

This means there won't be a 'preflight' OPTIONS check.

The simple content-types are:

 * application/x-www-form-urlencoded
 * multipart/form-data
 * text/plain


### Watch out for `application/json`!

Here's a big Gotcha - if your API speaks JSON, using `Content-Type: application/json` (for example), then that counts as an exotic content type, and you **will** be subject to a preflight OPTIONS request!

<img src="https://media.giphy.com/media/UWQYzdfhcsRpBCeMWC/source.gif" alt="Not who you were expecting">

### My call really is simple

Well, after calling for the endpoint you wanted, like `https://coolapi.example.com/pets/`, the browser checks whether the response contains an `Access-Control-Allow-Origin` header which lists your site by name or implies it by wildcard (that is, `*`).

If there's no such header, or your site isn't mentioned in said header, the browsers thinks "Ok, that API isn't supposed to be called from here (perhaps an attacker is trying to scrape user information)" and it stops the running JavaScript from seeing any detail about the response except that it failed. The F12 developer tools in the browser can tell the developer/user what happened, but the (potentially evil) script is kept in the dark.

So, to allow calls to your API from any and all websites, as long as you don't require special headers or [anything else mentioned on the MDN description of a simple request][simp], you only have to make sure that your server returns the aforementioned `Access-Control-Allow-Origin: *` header.


## 2. Complex requests

![CORS warning in F12 console](https://thepracticaldev.s3.amazonaws.com/i/ilcz0ede5myr9vb70mgr.png)

Complex, or "preflighted" requests are those with extra headers or an unusual content type, and have to be checked first (by the browser) to find out whether the request is safe to send at all.

When the browser thinks a request is complex, it will call ahead to the server with the HTTP `OPTIONS` verb.

Your server must respond to the OPTIONS verb not only with a matching `Access-Control-Allow-Origin` but with other headers that explicitly allow whatever incoming stuff you expect in the request. For example, if you expect a header called `X-Secret-Allergies` then your server must respond to the OPTIONS call with a header like:

```
Access-Control-Allow-Headers: X-Secret-Allergies
```

To allow content types that aren't in the "simple" list above, you have to explicitly add the `Content-Type` header to the list in `Access-Control-Allow-Headers`!


### A further complication - `Authorization` header and cookies!

If your request requires an Authorization header, or an auth cookie of some kind, you **can't use a wildcard** for your `Allow-Origins` list! Yikes! You have to specify domains. I don't know how people are working around this in the wild, except perhaps by rolling their own auth headers or doing some RESTful credentials-in-every-request.

If you're using a framework to abstract HTTP requests, like Axios, Angular `$http`, or (cough) JQuery AJAX, then you should look for the `withCredentials` option. Setting it to **true** means that you **are** sending either an Authorization header or an auth cookie. So you can't have a wildcard allow list, and you must add `Authorization` to your `Access-Control-Allow-Headers` list.


## 3. Why. What. Why do I have to do this. Wh-

Here is the [best explanation of an attack which is stopped by CORS][attack] that I have found.

It seems to me that in essence, CORS helps to protect users from evil sites which try to load resources from good sites, hoping that the user is logged into the good site, so that their account information can be pulled across to this evil page and sent off to an evil server.


## 4. Testing tool

Check out <https://cors-tester.glitch.me/>

{% glitch cors-tester %}

There may be plenty of tools out there for testing CORS, but I'd like to add mine to the pile.

This is an open source tool hosted on Glitch, which keeps your requests/responses entirely private; they go straight from your browser to whatever API you type in. If that's not good enough, you can even download the two files and run `index.html` on your own PC by simply opening it in a browser (no local server required)


## 5. End

I hope this article and the tool help you out.

Tell me about your CORS nightmares in the comments!

*Originally published at [stegriff.co.uk](https://stegriff.co.uk/upblog/dealing-with-cors/)*

[simp]: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#Simple_requests
[attack]: https://security.stackexchange.com/a/149169