1191595 - Add CORS headers for mozvr.com bucket

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Casey Yee]

We are hosting video files too large to fit onto github.io and will need CORS setup to source them from mozvr.com.

Here's a CORS configuration that should work:

<CORSConfiguration>
    <CORSRule>
        <AllowedOrigin>http://mozvr.github.io</AllowedOrigin>
        <AllowedMethod>GET</AllowedMethod>
        <MaxAgeSeconds>2592000</MaxAgeSeconds>
        <AllowedHeader>*</AllowedHeader>
    </CORSRule>
</CORSConfiguration>

The page that will be requesting the files:
http://mozvr.github.io/polarsea

Here's the <video> source elements:
https://github.com/MozVR/polarsea/blob/master/index.html#L137-L138

Comment 1

[Tanner Filip [:tanner]]

Not sure if this is the right component, but someone in MOC should know where to put it if it's not.

Comment 2

[Jake Maul [:jakem]]

This is applied. I don't know how long it takes for it to take effect, I'm guessing nearly-instantaneous... so you should be good now.

For future reference, this is set on the S3 bucket "mozvr.com", under the "Mozilla Web Ops - 1400" AWS account. Corey Shields is the contact listed on the account.

Comment 3

[Casey Yee]

Looks to be working.   Thanks Jake!

Comment 4

[Christopher Van Wiemeersch [:cvan]]

For some reason, I don't see any `Access-Control-*` headers set on this response:

% curl 'http://mozvr.com/projects/polarsea/content/videos/PolarSeaTrailer-3.mp4' -I
HTTP/1.1 200 OK
x-amz-id-2: i57t6jZxWWmZ3nKIyIelaufHnD6GCEu1WP47XXLjD+EXztF2w0yDHfPWfua67SJ75m7n8m16PM4=
x-amz-request-id: F80AFAD9ECD59ECA
Date: Fri, 14 Aug 2015 23:11:04 GMT
x-amz-meta-s3cmd-attrs: uid:502/gname:staff/uname:casey/gid:20/mode:33188/mtime:1421787833/atime:1421787832/ctime:1421787833
Last-Modified: Tue, 20 Jan 2015 21:07:21 GMT
ETag: "c36d8d3ceef7d44fafa179c95a5c46cb"
Content-Type: video/mp4
Content-Length: 100655303
Server: AmazonS3

Which routes are the CORS headers set for? Thanks!

Comment 5

[Jake Maul [:jakem]]

Sorry for the delay.

That file doesn't exist anymore, but offhand suspect the problem is "curl -I". This actually causes curl to send a HEAD request rather than a GET. If you check the CORS config in comment 0, it looks to be specific to GET requests.

If you're still running into issues, try this instead:

curl -v 'http://mozvr.com/projects/polarsea/content/videos/PolarSeaTrailer-3.mp4' -o /dev/null

Of course with a file that actually exists. :)

This fetches the whole file, so you may want to Ctrl-C once you get the headers.