By Dallas Clark

2014-08-30 00:50:44 8 Comments

I'm receiving the following error on a couple of Chrome browsers but not all. Not sure entirely what the issue is at this point.

Font from origin '' has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '' is therefore not allowed access.

I have the following CORS Configuration on S3


The request

Remote Address:
Request URL:
Request Method:GET
Status Code:200 OK
Request Headers
User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.94 Safari/537.36

All other requests from Cloudfront/S3 work properly, including JS files.


@Daksh Patel 2020-04-28 18:22:56

Just add use of origin in your if you use node.js as server...

like this

  app.use((req, res, next) => {
  res.header('Access-Control-Allow-Origin', '*');

We Need response for origin

@mihserf 2015-07-27 19:43:26

Working solution for heroku is here (quotes follow):

Below is exactly what you can do if you are running your Rails app in Heroku and using Cloudfront as your CDN. It was tested on Ruby 2.1 + Rails 4, Heroku Cedar stack.

Add CORS HTTP headers (Access-Control-*) to font assets

  • Add gem font_assets to Gemfile .
  • bundle install
  • Add config.font_assets.origin = '*' to config/application.rb . If you want more granular control, you can add different origin values to different environment, e.g., config/config/environments/production.rb
  • curl -I http://localhost:3000/assets/your-custom-font.ttf
  • Push code to Heroku.

Configure Cloudfront to forward CORS HTTP headers

In Cloudfront, select your distribution, under "behavior" tab, select and edit the entry that controls your fonts delivery (for most simple Rails app you only have 1 entry here). Change Forward Headers from "None" to "Whilelist". And add the following headers to whitelist:


Save it and that's it!

Caveat: I found that sometimes Firefox wouldn't not refresh the fonts even if CORS error is gone. In this case keep refreshing the page a few times to convince Firefox that you are really determined.

@bPratik 2015-11-17 11:56:23

Please avoid link-only answers. It will be helpful if you could copy relevant snippets out of the linked article into your answer. Thanks.

@nu everest 2017-11-02 14:45:38

For those using Microsoft products with a web.config file:

Merge this with your web.config.

To allow on any domain replace value="domain" with value="*"

<?xml version="1.0" encoding="utf-8" ?>
        <add name="Access-Control-Allow-Origin" value="domain" />

If you don't have permission to edit web.config, then add this line in your server-side code.

Response.AppendHeader("Access-Control-Allow-Origin", "domain");

@mohrtan 2019-10-08 17:39:42

Deserves a vote up for remembering us Windows users.

@Yusuff Sodiq 2020-05-24 19:39:48

I'm using core, how do I add this to the appsettings.json file?

@agbodike 2017-05-13 00:34:40

I had this same problem and this link provided the solution for me:

The short version of it is:

  1. Edit S3 CORS config (my code sample didn't display properly)
    Note: This is already done in the original question
    Note: the code provided is not very secure, more info in the linked page.
  2. Go to the "Behaviors" tab of your distribution and click to edit
  3. Change "Forward Headers" from “None (Improves Caching)” to “Whitelist.”
  4. Add “Origin” to the "Whitelist Headers" list
  5. Save the changes

Your cloudfront distribution will update, which takes about 10 minutes. After that, all should be well, you can verify by checking that the CORS related error messages are gone from the browser.

@Özer S. 2016-12-29 22:14:00

I was able to solve the problem by simply adding <AllowedMethod>HEAD</AllowedMethod> to the CORS policy of the S3 Bucket.


<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="">

@Özer S. 2017-10-20 15:17:15

not sure about security though, would be nice if someone had some input on that..

@Salvatore Iovene 2017-11-01 16:38:09

Doe this change need time to propagate? I just added <AllowedMethod>HEAD</AllowedMethod> to my CORS policy on the bucket and it's still not working.

@Özer S. 2017-11-01 22:53:43

usually no, it should take max. couple minutes

@Michael Cole 2016-11-29 02:10:21

There is a nice writeup here.

Configuring this in nginx/apache is a mistake.
If you are using a hosting company you can't configure the edge.
If you are using Docker, the app should be self contained.

Note that some examples use connectHandlers but this only sets headers on the doc. Using rawConnectHandlers applies to all assets served (fonts/css/etc).

  // HSTS only the document - don't function over http.  
  // Make sure you want this as it won't go away for 30 days.
  WebApp.connectHandlers.use(function(req, res, next) {
    res.setHeader('Strict-Transport-Security', 'max-age=2592000; includeSubDomains'); // 2592000s / 30 days

  // CORS all assets served (fonts/etc)
  WebApp.rawConnectHandlers.use(function(req, res, next) {
    res.setHeader('Access-Control-Allow-Origin', '*');
    return next();

This would be a good time to look at browser policy like framing, etc.

@KBH 2015-03-17 06:03:50

On June 26, 2014 AWS released proper Vary: Origin behavior on CloudFront so now you just

Set a CORS Configuration for your S3 bucket:


In CloudFront -> Distribution -> Behaviors for this origin, use the Forward Headers: Whitelist option and whitelist the 'Origin' header.

Wait for ~20 minutes while CloudFront propagates the new rule

Now your CloudFront distribution should cache different responses (with proper CORS headers) for different client Origin headers.

@Jaco Pretorius 2015-06-12 17:02:13

This doesn't seem to work, do you have more details? I enabled this but I still get exactly the same issue.

@Luigi04 2016-02-01 21:40:13

The only thing that has worked for me (probably because I had inconsistencies with www. usage):

Paste this in to your .htaccess file:

<IfModule mod_headers.c>
<FilesMatch "\.(eot|font.css|otf|ttc|ttf|woff)$">
    Header set Access-Control-Allow-Origin "*"
<IfModule mod_mime.c>
# Web fonts
AddType application/font-woff woff
AddType application/ eot

# Browsers usually ignore the font MIME types and sniff the content,
# however, Chrome shows a warning if other MIME types are used for the
# following fonts.
AddType application/x-font-ttf ttc ttf
AddType font/opentype otf

# Make SVGZ fonts work on iPad:
AddType     image/svg+xml svg svgz
AddEncoding gzip svgz


# rewrite →

<IfModule mod_rewrite.c>
RewriteCond %{HTTPS} !=on
RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
RewriteRule ^ http://%1%{REQUEST_URI} [R=301,L]

@Rotimi 2019-10-28 11:40:06

Awesome! Thanks alot!

@Mohammed Moinuddin Waseem 2019-11-27 05:10:46

Since your code was detailed, it took some time for me to go through it, I learned few things though. I applied portion of it to tweak my solution. It worked.

@Yaniv Vova Alterman 2015-07-04 00:12:14


location ~* \.(eot|ttf|woff)$ {
   add_header Access-Control-Allow-Origin '*';


  1. Select your bucket
  2. Click properties on the right top
  3. Permisions => Edit Cors Configuration => Save
  4. Save

@neobie 2017-08-08 05:26:18

after adding this, get 404 not found.

@Giovanni Di Gregorio 2015-01-30 13:27:26

Add this rule to your .htaccess

Header add Access-Control-Allow-Origin "*" 

even better, as suggested by @david thomas, you can use a specific domain value, e.g.

Header add Access-Control-Allow-Origin ""

@NineCattoRules 2015-03-26 23:17:52

Hi, what's the difference with Header set Access-Control-Allow-Origin "*" ? Thanks

@Arsalan Saleem 2015-04-09 11:38:18

for windows people, set <add name="Access-Control-Allow-Origin" value="*" /> under <customHeaders> in web.config file. Have a nice day

@Giovanni Di Gregorio 2015-04-13 20:02:25

@Simone the difference is that with "add" the response header is added to the existing set of headers, even if this header already exists. This can result in two (or more) headers having the same name; whereas with "set" the response header is set, replacing any previous header with this name. In this case is the same cause * includes them all.

@NineCattoRules 2015-04-14 08:56:55

@GiovanniDiGregorio Thanks for the nice info!

@David Thomas 2015-05-12 08:11:51

Just noting Access-Control-Allow-Origin "*" is potentially insecure as it opens the domain to javascript access from any domain. You should use a specific domain value instead, e.g Access-Control-Allow-Origin "" See also for a good explanation.

@Tim Diggins 2014-09-06 07:48:55

Chrome since ~Sep/Oct 2014 makes fonts subject to the same CORS checks as Firefox has done There is a discussion on this in!topic/blink-dev/TT9D5-Zfnzw

Given that for fonts the browser may do a preflight check, then your S3 policy needs the cors request header as well. You can check your page in say Safari (which at present doesn't do CORS checking for fonts) and Firefox (that does) to double check this is the problem described.

See Stack overflow answer on Amazon S3 CORS (Cross-Origin Resource Sharing) and Firefox cross-domain font loading for the Amazon S3 CORS details.

NB in general because this used to apply to Firefox only, so it may help to search for Firefox rather than Chrome.

@Dallas Clark 2014-09-07 23:58:19

Thanks for this answer, looks like it may be a problem for many others. Although my problem was occurring in a stable build of Chrome.

@justingordon 2014-09-23 06:34:56

This is happening in Chrome now.

@Tim Diggins 2015-01-21 17:31:28

As people keep referring (including myself!) to this answer, I've made it less historical and more relevant to present day.

@Tim Diggins 2015-01-21 17:31:43

Also FYI I discovered that a error message "has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin" was actually to do with having a bad path to a font file in my original server, and cloudfront then redirecting to the homepage of my server (and either the redirect response or the homepage didn't have the CORS headers). Confusing, but solved by using the correct path to the actual font file (not a CORS issue, strictly speaking).

@Dan 2015-03-31 18:04:13

Hey @DallasClark, you may want to choose an accepted answer for your question. Thanks Tim, your links and explanations were helpful in my experience. Cheers.

Related Questions

Sponsored Content

1 Answered Questions

2 Answered Questions

1 Answered Questions

[SOLVED] AWS S3 static site CORS jquery ajax POST to API Gateway

2 Answered Questions

[SOLVED] CORS: No pre-flight on GET but a pre-flight on POST

1 Answered Questions

Cross Origin call is not allowing in browser

2 Answered Questions

Cookie not sent in Chrome Cross Domain Post

Sponsored Content