You cannot put multiple domains here (how to restrict to multiple domains is explained further down) Access-Control-Allow-Origin: the domain allowed, * allows ALL domains.So, we need to make sure that when an OPTIONS request is sent to our Nginx server, that we respond back with the correct headers. This is why if you sent a POST request to another server, you will also see an OPTIONS request sent first.

This basically just asks the server if it will allow the request and it’s sent in the form of an OPTIONS request. When a site tries to request access to resources from another site, it will first of all send a preflight request. Now this will be the configuration file that will be used on the nginx server. As we need a custom configuration file, copy the contents of into a nf file in your root Magento folder. By default the will mount the default Magento file as your default configuration file. If you already have Magento up and running and you just want to look at the final configuration file settings then you can skip this section.įor my setup I user docker compose using Mark Shust’s configuration and Magento community edition is installed via composer. This tutorial is only for a server running Nginx. So for example, if your front end application is on one domain and it needs to access an API on another domain, you must setup the access headers on the API server. You will need to send specific headers from the application that is being accessed. If you are running applications on different subdomains and/or domains and they need to talk to each other, then you will need to setup CORS. After spending a while fighting CORS issues using a headless Magento 2 setup, here is how I solved the issue using nfīefore jumping into a solution, I think it’s important to understand what is happening and whyĬORS stands for Cross-Origin Resource Sharing and it basically controls which sites can access the resources of another site.

Nginx access control allow origin