blocks|key|487082|text|是的，当然。Firefox支持字体的CORS，就像http://dev.w3.org/csswg/css3-fonts/#allowing-cross-origin-font-loading的规范要求一样|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|487083|entityMap|0|LINK|mutability|MUTABLE|url|http://dev.w3.org/csswg/css3-fonts/#allowing-cross-origin-font-loading^0|P|1Y|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Yes, of course. Firefox supports CORS for fonts, just like the spec requires at <a href="http://dev.w3.org/csswg/css3-fonts/#allowing-cross-origin-font-loading" rel="nofollow">http://dev.w3.org/csswg/css3-fonts/#allowing-cross-origin-font-loading</a>

blocks|key|487134|text|文档指出，您可以将该配置作为“存储桶中的cors子资源”。我认为这意味着我将使用配置在存储桶的根目录下创建一个名为"cors“的文件，但这将不起作用。最后，我必须登录到亚马逊S3管理区域，并在我的存储桶的properties对话框中添加配置。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|487135|S3可以使用一些更好的文档...|487136|entityMap^0|2U|A|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Well, the documentation states that you can stick the configuration as "the cors subresource in your bucket." I took this to mean I would create a file called "cors" at the root of my bucket with the configuration, but this would not work. In the end I had to login to the Amazon S3 administration area and add the configuration within the <code>properties</code> dialog of my bucket.

S3 could use some better documentation...

blocks|key|487185|text|在我的例子中，我没有在CORS配置中定义XML名称空间和版本。定义那些有效的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|487186|变化|487187|<CORSConfiguration>|code-block|syntax|javascript|487188|至|487189|<?xml+version="1.0"+encoding="UTF-8"?>
<CORSConfiguration+xmlns="http://s3.amazonaws.com/doc/2006-03-01/">|487190|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

In my case, I hadn't defined XML namespace and version in CORS configuration. Defining those worked.

Changed

<pre><code>&lt;CORSConfiguration&gt;
</code></pre>

to

<pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"&gt;
</code></pre>

blocks|key|270329|text|经过一些调整之后，我似乎已经在没有查询字符串hack的情况下工作了。更多信息请点击此处：http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/RequestAndResponseBehaviorS3Origin.html#RequestS3-cors|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|270330|我将通过我的整个设置，以便很容易地看到我做了什么，希望这能帮助其他人。|270331|背景信息:我正在使用一个包含asset_sync+gem的Rails应用程序将资源放到S3上。这包括字体。|270332|在S3控制台中，我点击了我的存储桶、属性和“编辑cors配置”，这里：|270333|📷|atomic|270334|​|270335|在文本区域中，我有类似这样的东西：|270336|<?xml+version="1.0"+encoding="UTF-8"?>
<CORSConfiguration+xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
++++<CORSRule>
++++++++<AllowedOrigin>https://*.example.com</AllowedOrigin>
++++++++<AllowedMethod>GET</AllowedMethod>
++++++++<MaxAgeSeconds>3000</MaxAgeSeconds>
++++++++<AllowedHeader>*</AllowedHeader>
++++</CORSRule>
</CORSConfiguration>|code-block|syntax|javascript|270337|然后在云前端面板(https://console.aws.amazon.com/cloudfront/home)中，我创建了一个发布，添加了一个指向我的S3存储桶的原点|270338|270339|270340|然后添加了默认路径的行为，以指向基于S3的源I设置。我还点击了白名单标题并添加了Origin：|style|CODE|270341|270342|270343|现在发生的事情是这样的，我相信这是正确的：|270344|1)检查S3报头设置是否正确|270345|curl+-i+-H+"Origin:+https://example.com"+https://s3.amazonaws.com/xxxxxxxxx/assets/fonts/my-cool-font.ttf
HTTP/1.1+200+OK
x-amz-id-2:+Ay63Qb5uR98ag47SRJ91%2BYALtc4onRu1JUJgMTU98Es/pzQ3ckmuWhzzbTgDTCt%2B
x-amz-request-id:+F1FFE275C0FBE500
Date:+Thu,+14+Aug+2014+09:39:40+GMT
Access-Control-Allow-Origin:+https://example.com
Access-Control-Allow-Methods:+GET
Access-Control-Max-Age:+3000
Access-Control-Allow-Credentials:+true
Vary:+Origin,+Access-Control-Request-Headers,+Access-Control-Request-Method
Cache-Control:+public,+must-revalidate,+proxy-revalidate,+max-age=180
Last-Modified:+Mon,+09+Dec+2013+14:29:04+GMT
ETag:+"98918ee7f339c7534c34b9f5a448c3e2"
Accept-Ranges:+bytes
Content-Type:+application/x-font-ttf
Content-Length:+12156
Server:+AmazonS3|270346|2)检查Cloudfront是否与报头一起工作|270347|curl+-i+-H+"Origin:+https://example.com"+https://xxxxx.cloudfront.net/assets/fonts/my-cool-font.ttf
HTTP/1.1+200+OK
Content-Type:+application/x-font-ttf
Content-Length:+12156
Connection:+keep-alive
Date:+Thu,+14+Aug+2014+09:35:26+GMT
Access-Control-Allow-Origin:+https://example.com
Access-Control-Allow-Methods:+GET
Access-Control-Max-Age:+3000
Access-Control-Allow-Credentials:+true
Cache-Control:+public,+must-revalidate,+proxy-revalidate,+max-age=180
Last-Modified:+Mon,+09+Dec+2013+14:29:04+GMT
ETag:+"98918ee7f339c7534c34b9f5a448c3e2"
Accept-Ranges:+bytes
Server:+AmazonS3
Vary:+Origin
X-Cache:+Miss+from+cloudfront
Via:+1.1+77bdacfea247b6cbe84dffa61da5a554.cloudfront.net+(CloudFront)
X-Amz-Cf-Id:+cmCxaUcFf3bT48zpPw0Q-vDDza0nZoWm9-_3qY5pJBhj64iTpkgMlg==|270348|(请注意，上面是cloudfront中的一个未命中，因为这些文件被缓存了180秒，但在命中时也是如此)|270349|3)使用不同的源(但在S3存储桶的CORS上允许的源)命中cloudfront+-+Access-Control-Allow-Origin未被缓存！耶！|270350|curl+-i+-H+"Origin:+https://www2.example.com"+https://xxxxx.cloudfront.net/assets/fonts/my-cool-font.ttf
HTTP/1.1+200+OK
Content-Type:+application/x-font-ttf
Content-Length:+12156
Connection:+keep-alive
Date:+Thu,+14+Aug+2014+10:02:33+GMT
Access-Control-Allow-Origin:+https://www2.example.com
Access-Control-Allow-Methods:+GET
Access-Control-Max-Age:+3000
Access-Control-Allow-Credentials:+true
Cache-Control:+public,+must-revalidate,+proxy-revalidate,+max-age=180
Last-Modified:+Mon,+09+Dec+2013+14:29:04+GMT
ETag:+"98918ee7f339c7534c34b9f5a448c3e2"
Accept-Ranges:+bytes
Server:+AmazonS3
Vary:+Origin
X-Cache:+Miss+from+cloudfront
Via:+1.1+ba7014bad8e9bf2ed075d09443dcc4f1.cloudfront.net+(CloudFront)
X-Amz-Cf-Id:+vy-UccJ094cjdbdT0tcKuil22XYwWdIECdBZ_5hqoTjr0tNH80NQPg==|270351|请注意，在没有查询字符串黑客攻击的情况下，域已成功更改。|270352|当我更改原始标头时，似乎总是在第一个请求上有一个X-Cache:+Miss+from+cloudfront，然后我得到了预期的X-Cache:+Hit+from+cloudfront|270353|附注:值得注意的是，当执行curl+-I+(大写I)时，不会显示Access-Control-Allow-Origin头部，因为它只是一个头部，我执行-i使其成为GET并向上滚动。|270354|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/RequestAndResponseBehaviorS3Origin.html#RequestS3-cors|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/adfc9c1b4968406f2cba1ed3d8863ec6.png|imageAlt|2|https://console.aws.amazon.com/cloudfront/home|3|https://ask.qcloudimg.com/http-save/yehe-900000/0b9d202f7c428d00517effa20c09ece8.png|4|https://ask.qcloudimg.com/http-save/yehe-900000/38d29f46c884de63fcd73d6f7d8c9d55.png^0|18|3C|0|0|0|0|0|0|1|1|0|0|0|0|9|1A|2|0|0|1|3|0|0|14|6|0|0|1|4|0|0|0|0|0|0|0|0|16|R|0|0|0|O|T|1R|S|0|0^^$0|@$1|2|3|4|5|6|7|2B|8|@]|9|@$A|2C|B|2D|1|2E]]|C|$]]|$1|D|3|E|5|6|7|2F|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|2G|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|2H|8|@]|9|@]|C|$]]|$1|J|3|K|5|L|7|2I|8|@]|9|@$A|2J|B|2K|1|2L]]|C|$]]|$1|M|3|N|5|6|7|2M|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|2N|8|@]|9|@]|C|$]]|$1|Q|3|R|5|S|7|2O|8|@]|9|@]|C|$T|U]]|$1|V|3|W|5|6|7|2P|8|@]|9|@$A|2Q|B|2R|1|2S]]|C|$]]|$1|X|3|K|5|L|7|2T|8|@]|9|@$A|2U|B|2V|1|2W]]|C|$]]|$1|Y|3|N|5|6|7|2X|8|@]|9|@]|C|$]]|$1|Z|3|10|5|6|7|2Y|8|@$A|2Z|B|30|11|12]]|9|@]|C|$]]|$1|13|3|K|5|L|7|31|8|@]|9|@$A|32|B|33|1|34]]|C|$]]|$1|14|3|N|5|6|7|35|8|@]|9|@]|C|$]]|$1|15|3|16|5|6|7|36|8|@]|9|@]|C|$]]|$1|17|3|18|5|6|7|37|8|@]|9|@]|C|$]]|$1|19|3|1A|5|S|7|38|8|@]|9|@]|C|$T|U]]|$1|1B|3|1C|5|6|7|39|8|@]|9|@]|C|$]]|$1|1D|3|1E|5|S|7|3A|8|@]|9|@]|C|$T|U]]|$1|1F|3|1G|5|6|7|3B|8|@]|9|@]|C|$]]|$1|1H|3|1I|5|6|7|3C|8|@$A|3D|B|3E|11|12]]|9|@]|C|$]]|$1|1J|3|1K|5|S|7|3F|8|@]|9|@]|C|$T|U]]|$1|1L|3|1M|5|6|7|3G|8|@]|9|@]|C|$]]|$1|1N|3|1O|5|6|7|3H|8|@$A|3I|B|3J|11|12]|$A|3K|B|3L|11|12]]|9|@]|C|$]]|$1|1P|3|1Q|5|6|7|3M|8|@]|9|@]|C|$]]|$1|1R|3|-4|5|6|7|3N|8|@]|9|@]|C|$]]]|1S|$1T|$5|1U|1V|1W|C|$1X|1Y]]|1Z|$5|20|1V|21|C|$22|23|24|-4]]|25|$5|1U|1V|1W|C|$1X|26]]|27|$5|20|1V|21|C|$22|28|24|-4]]|29|$5|20|1V|21|C|$22|2A|24|-4]]]]

After some tweaking I seem to have got this to work without the query string hack. More info here: <a href="http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/RequestAndResponseBehaviorS3Origin.html#RequestS3-cors" rel="noreferrer">http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/RequestAndResponseBehaviorS3Origin.html#RequestS3-cors</a>

I'm going to go through my entire setup so that it's easy to see what I've done, hopefully this helps others.

Background Information:
I'm using a Rails app that has the asset_sync gem to put assets onto S3. This includes fonts.

Within S3 console, I clicked on my bucket, properties and 'edit cors configuration', here: <img src="https://i.stack.imgur.com/PGuNA.png" alt="CORS config button">

Inside the textarea I have something like:

<pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"&gt;
 &lt;CORSRule&gt;
 &lt;AllowedOrigin&gt;https://*.example.com&lt;/AllowedOrigin&gt;
 &lt;AllowedMethod&gt;GET&lt;/AllowedMethod&gt;
 &lt;MaxAgeSeconds&gt;3000&lt;/MaxAgeSeconds&gt;
 &lt;AllowedHeader&gt;*&lt;/AllowedHeader&gt;
 &lt;/CORSRule&gt;
&lt;/CORSConfiguration&gt;
</code></pre>

Then within Cloudfront panel (<a href="https://console.aws.amazon.com/cloudfront/home" rel="noreferrer">https://console.aws.amazon.com/cloudfront/home</a>) I created a distribution, added an Origin that pointed to my S3 bucket 
<img src="https://i.stack.imgur.com/kTqYh.png" alt="adding an origin">

Then added a behavior for a default path to point to the S3 based origin I setup. What I also did was click on Whitelist headers and added <code>Origin</code>:
<img src="https://i.stack.imgur.com/JV9qe.png" alt="adding a behavior and whitelist headers">

What happens now is the following, which I believe is right:

1) Check that S3 headers are being set correctly

<pre><code>curl -i -H "Origin: https://example.com" https://s3.amazonaws.com/xxxxxxxxx/assets/fonts/my-cool-font.ttf
HTTP/1.1 200 OK
x-amz-id-2: Ay63Qb5uR98ag47SRJ91+YALtc4onRu1JUJgMTU98Es/pzQ3ckmuWhzzbTgDTCt+
x-amz-request-id: F1FFE275C0FBE500
Date: Thu, 14 Aug 2014 09:39:40 GMT
Access-Control-Allow-Origin: https://example.com
Access-Control-Allow-Methods: GET
Access-Control-Max-Age: 3000
Access-Control-Allow-Credentials: true
Vary: Origin, Access-Control-Request-Headers, Access-Control-Request-Method
Cache-Control: public, must-revalidate, proxy-revalidate, max-age=180
Last-Modified: Mon, 09 Dec 2013 14:29:04 GMT
ETag: "98918ee7f339c7534c34b9f5a448c3e2"
Accept-Ranges: bytes
Content-Type: application/x-font-ttf
Content-Length: 12156
Server: AmazonS3
</code></pre>

2) Check Cloudfront works with the headers

<pre><code>curl -i -H "Origin: https://example.com" https://xxxxx.cloudfront.net/assets/fonts/my-cool-font.ttf
HTTP/1.1 200 OK
Content-Type: application/x-font-ttf
Content-Length: 12156
Connection: keep-alive
Date: Thu, 14 Aug 2014 09:35:26 GMT
Access-Control-Allow-Origin: https://example.com
Access-Control-Allow-Methods: GET
Access-Control-Max-Age: 3000
Access-Control-Allow-Credentials: true
Cache-Control: public, must-revalidate, proxy-revalidate, max-age=180
Last-Modified: Mon, 09 Dec 2013 14:29:04 GMT
ETag: "98918ee7f339c7534c34b9f5a448c3e2"
Accept-Ranges: bytes
Server: AmazonS3
Vary: Origin
X-Cache: Miss from cloudfront
Via: 1.1 77bdacfea247b6cbe84dffa61da5a554.cloudfront.net (CloudFront)
X-Amz-Cf-Id: cmCxaUcFf3bT48zpPw0Q-vDDza0nZoWm9-_3qY5pJBhj64iTpkgMlg==
</code></pre>

(Note the above was a miss from cloudfront because these files are cached for 180 seconds, but the same was working on hits)

3) Hit cloudfront with a different origin (but one that is allowed on CORS for the S3 bucket) - the <code>Access-Control-Allow-Origin</code> is not cached! yay!

<pre><code>curl -i -H "Origin: https://www2.example.com" https://xxxxx.cloudfront.net/assets/fonts/my-cool-font.ttf
HTTP/1.1 200 OK
Content-Type: application/x-font-ttf
Content-Length: 12156
Connection: keep-alive
Date: Thu, 14 Aug 2014 10:02:33 GMT
Access-Control-Allow-Origin: https://www2.example.com
Access-Control-Allow-Methods: GET
Access-Control-Max-Age: 3000
Access-Control-Allow-Credentials: true
Cache-Control: public, must-revalidate, proxy-revalidate, max-age=180
Last-Modified: Mon, 09 Dec 2013 14:29:04 GMT
ETag: "98918ee7f339c7534c34b9f5a448c3e2"
Accept-Ranges: bytes
Server: AmazonS3
Vary: Origin
X-Cache: Miss from cloudfront
Via: 1.1 ba7014bad8e9bf2ed075d09443dcc4f1.cloudfront.net (CloudFront)
X-Amz-Cf-Id: vy-UccJ094cjdbdT0tcKuil22XYwWdIECdBZ_5hqoTjr0tNH80NQPg==
</code></pre>

Note above that the domain has successfully changed without a query string hack.

When I change the Origin header, there seems to always be a <code>X-Cache: Miss from cloudfront</code> on the first request then afterwards I get the expected <code>X-Cache: Hit from cloudfront</code>

P.S. It is worth noting that when doing curl -I (capital I) will NOT show the Access-Control-Allow-Origin headers as it only a HEAD, I do -i to make it a GET and scroll up.

blocks|key|487561|text|有一种更好更简单的方法！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|487562|我个人更喜欢使用我的DNS子域来解决这个问题。如果我的CDN是在cdn.myawesomeapp.com后面，而不是sdf73n7ssa.cloudfront.net后面，那么浏览器就不会因为跨域安全问题而抓狂和阻止它们。|487563|要将您的子域指向您的AWS+Cloudfront域，请转到AWS+Cloudfront控制面板，选择您的Cloudfront分发版，然后在备用域名(CNAME)字段中输入您的CDN子域。像cdn.myawesomeapp.com这样的东西就可以了。|487564|现在您可以转到您的域名服务提供商(如AWS+Route+53)，为指向sdf73n7ssa.cloudfront.net的cdn.myawesomeapp.com创建一个CNAME。|487565|http://blog.cloud66.com/cross-origin-resource-sharing-cors-blocked-for-cloudfront-in-rails/|offset|length|487566|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|2J|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@$J|X|K|Y|1|Z]]|A|$]]|$1|L|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|I]]]]

There is a better and easier way!

I personally prefer using my DNS subdomains to solve this problem. If my CDN is behind cdn.myawesomeapp.com instead of sdf73n7ssa.cloudfront.net then browsers are not going to freakout and block them as cross domain security problems.

To point your subdomain to your AWS Cloudfront domain go to AWS Cloudfront control panel, select your Cloudfront distribution and enter your CDN subdomain into the Alternate Domain Names (CNAMEs) field. Something like cdn.myawesomeapp.com will do.

Now you can go to your DNS provider (like AWS Route 53) and create a CNAME for cdn.myawesomeapp.com pointing to sdf73n7ssa.cloudfront.net.

<a href="http://blog.cloud66.com/cross-origin-resource-sharing-cors-blocked-for-cloudfront-in-rails/" rel="noreferrer">http://blog.cloud66.com/cross-origin-resource-sharing-cors-blocked-for-cloudfront-in-rails/</a>

blocks|key|487570|text|<ifModule+mod_headers.c>

+++Header+set+Access-Control-Allow-Origin:+http://domainurl.com

</ifModule>|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|487571|简单解决方案|unstyled|487572|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>&lt;ifModule mod_headers.c&gt;

 Header set Access-Control-Allow-Origin: http://domainurl.com

&lt;/ifModule&gt;
</code></pre>

Simple Solution

blocks|key|270528|text|这个配置对我很有效。我可以列出对象，检索，更新和删除。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|270529|<?xml+version="1.0"+encoding="UTF-8"?>
<CORSConfiguration+xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
++<CORSRule>
++++<AllowedOrigin>http://localhost:3000</AllowedOrigin>
++++<AllowedMethod>HEAD</AllowedMethod>
++++<AllowedMethod>GET</AllowedMethod>
++++<AllowedMethod>PUT</AllowedMethod>
++++<AllowedMethod>POST</AllowedMethod>
++++<AllowedMethod>DELETE</AllowedMethod>
++++<AllowedHeader>*</AllowedHeader>
++++<ExposeHeader>ETag</ExposeHeader>
++++<ExposeHeader>x-amz-meta-custom-header</ExposeHeader>
++</CORSRule>
</CORSConfiguration>|code-block|syntax|javascript|270530|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This configuration worked for me. I can list object, retrieve, update and delete.

<pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"&gt;
 &lt;CORSRule&gt;
 &lt;AllowedOrigin&gt;http://localhost:3000&lt;/AllowedOrigin&gt;
 &lt;AllowedMethod&gt;HEAD&lt;/AllowedMethod&gt;
 &lt;AllowedMethod&gt;GET&lt;/AllowedMethod&gt;
 &lt;AllowedMethod&gt;PUT&lt;/AllowedMethod&gt;
 &lt;AllowedMethod&gt;POST&lt;/AllowedMethod&gt;
 &lt;AllowedMethod&gt;DELETE&lt;/AllowedMethod&gt;
 &lt;AllowedHeader&gt;*&lt;/AllowedHeader&gt;
 &lt;ExposeHeader&gt;ETag&lt;/ExposeHeader&gt;
 &lt;ExposeHeader&gt;x-amz-meta-custom-header&lt;/ExposeHeader&gt;
 &lt;/CORSRule&gt;
&lt;/CORSConfiguration&gt;
</code></pre>

blocks|key|487623|text|重新启动我的spring+boot应用程序(服务器)为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|487624|我已经在S3上正确配置了CORS。curl使用原始头给出了正确的响应。Safari正在正确获取字体。这只是铬谁不愿意接受CORS。|487625|不确定到底是什么导致了这种行为。一定是和If-modified-since有关|487626|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Restarting my spring boot application (server) solved the problem for me.

I had configured CORS correctly on S3.
The curl was giving the correct response with origin header.
Safari was fetching the font correctly.
It was only the chrome who was not willing to accept the CORS.

Not sure what exactly caused the behaviour.
Must be something to do with If-modified-since

There has been a long standing issue with Firefox not loading font from different origin than the current webpage. Usually, the issue arise when the fonts are served on CDNs.

Various solutions has been raised in other questions:

<a href="https://stackoverflow.com/questions/2856502/css-font-face-not-working-with-firefox-but-working-with-chrome-and-ie">CSS @font-face not working with Firefox, but working with Chrome and IE</a>

With the introduction of Amazon S3 CORS, is there a solution using CORS to address the font loading issue in Firefox?

edit: It would be great to see a sample of the S3 CORS configuration.

edit2: I have found a working solution without actually understanding what it did. If anyone could provide more detailed explanations about the configs and the background magic that happens on Amazon's interpretation of the config, it will be greatly appreciated, as with nzifnab who put up a bounty for it.

Amazon S3 CORS (Cross-Origin Resource Sharing) and Firefox cross-domain font loading

Firefox无法加载与当前网页不同来源的字体，这是一个长期存在的问题。通常，当在CDN上提供字体时，问题就会出现。在其他问题中提出了各种解决方案：随着Amazon的引入，有没有使用CORS来解决S3中字体加载问题的解决方案？编辑:如果能看到S3 CORS配置的示例，那就太好了。edit2:我发现了一个有效的解决方案，...

问亚马逊火狐CORS (跨域资源共享)和S3跨域字体加载
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问亚马逊火狐CORS (跨域资源共享)和S3跨域字体加载EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问亚马逊火狐CORS (跨域资源共享)和S3跨域字体加载
EN