title: CORS problems with Amazon S3 on the latest Chomium and Google Canary
body: <p>Our website is having problems loading CSS and JS resources on a Amazon S3 bucket with the very latest version of Chromium (Version 33.0.1722.0 - 237596) and Chrome Canary.
  It works well with any of the other browsers including the current Chrome (31.0.1650.57).</p>
  
  <p>The error is:</p>
  
  <p><em>Script from origin '<a href="https://mybucket.s3.amazonaws.com" rel="noreferrer">https://mybucket.s3.amazonaws.com</a>' has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '<a href="https://app.example.com" rel="noreferrer">https://app.example.com</a>' is therefore not allowed access.</em></p>
  
  <p>Our S3 CORS configuration on the resource bucket is:</p>
  
  <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;*&lt;/AllowedOrigin&gt;
          &lt;AllowedMethod&gt;GET&lt;/AllowedMethod&gt;
          &lt;MaxAgeSeconds&gt;300000&lt;/MaxAgeSeconds&gt;
          &lt;AllowedHeader&gt;Authorization&lt;/AllowedHeader&gt;
      &lt;/CORSRule&gt;
  &lt;/CORSConfiguration&gt;
  </code></pre>
  
  <p>Is it a bug with Chromium? 
  Did something change on the latest CORS spec?</p>