-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How can I get S3 to use correct MIME types for static content? #73
Comments
Oooh wait this is CORB not CORS.... |
From reading https://www.chromium.org/Home/chromium-security/corb-for-developers it looks like the MIME type being sent incorrectly from S3 is causing the issue. How can I get S3 to use correct MIME types for static content? |
Could be a bug w upload code in deploy. You can change mimes in the S3 console. Just walking but will be atta machine shortly |
Thanks for the quick reply, that would be cool. I'll get into the console now. Am I right that /static has to be flat? |
Nope! Just can't have empty folders is all |
Opening
To:
And running
Which appear correct. However those files (unlike the ones above) do not appear in the S3 console. Is there some better way to redeploy static than |
PS the bug is a slash normalisation issue:
Is Let's call that
Is Note the different slashes. So that solves the first part (I'll send a PR). But why is the deploy not working? |
I think I'm good for this, hitting dance/gym now but PR incoming later tonight |
Also for my own ref (and maybe yours): nodejs/node#8237 |
huh, TIL |
OK But content types still aren't being set properly (everything is Setting content type manually doesn't work either: It's getting late here now so can check again in morning, but if you have any ideas re: content types (maybe check out and deploy https://github.com/arc-repos/arc-example-notes) it would be useful. |
This is resolved (once the PR is merged) now - I wiped and remade the bucket, used the code in the PR to Please close once architect/architect#269 is merged. |
Actually going to close this anyway since it's for the wrong repo. |
This is probably a documentation issue. As in, I don't understand how to do something and the current static docs don't tell me.
Quick question
Minor note: the docs don't cover this, but since S3 doesn't have 'real' folders (and looking at the other arc-examples), I guess
/static
should be flat and not have folders (folders do work on sandbox though, which is why I'm confused). Is that correct?Issue
Source code: https://github.com/arc-repos/arc-example-notes, using arc 4.5.6
On sandbox:
On staging:
CORB error:
Edit: Note this is CORB not CORS.
The text was updated successfully, but these errors were encountered: