title: CORS Issue with woff2 fonts behind CDN in Chrome
body: <p>I have an S3 Bucket fronted with a Cloudfront CDN. In that bucket, I have some woff2 fonts that were automatically tagged with the content type <code>octet-stream</code>. When trying to load that font from a CSS file on a live production website, I get the following error:</p>
  
  <pre><code>Access to Font at 'https://cdn.example.com/fonts/my-font.woff2' from origin 
  'https://www.live-website.com' has been blocked by CORS policy: 
  No 'Access-Control-Allow-Origin' header is present on the requested resource. 
  Origin 'https://www.live-website.com' is therefore not allowed access.
  </code></pre>
  
  <p>The thing is that a curl reveals that the <code>Access-Control-Allow-Origin</code> is present:</p>
  
  <pre><code>HTTP/1.1 200 OK
  Content-Type: binary/octet-stream
  Content-Length: 98488
  Connection: keep-alive
  Date: Wed, 08 Aug 2018 19:43:01 GMT
  Access-Control-Allow-Origin: *
  Access-Control-Allow-Methods: GET
  Access-Control-Max-Age: 3000
  Last-Modified: Mon, 14 Aug 2017 14:57:06 GMT
  ETag: "&lt;redacted&gt;"
  Accept-Ranges: bytes
  Server: AmazonS3
  Age: 84847
  X-Cache: Hit from cloudfront
  Via: 1.1 &lt;redacted&gt;
  X-Amz-Cf-Id: &lt;redacted&gt;
  </code></pre>
  
  <p>Everything is working fine in Firefox, so I guess that Chrome is doing an extra validation that blocks my font.</p>