Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
(@aws-cdk/aws-s3-deployment): wrong MIME type for WebAssembly files
See original GitHub issueWhen using the BucketDeployment we have small options to include and exclude. Somehow we are not getting it right. The origin lays in the fact that aws s3 is serving .wasm files as wrong MIME type namely content-type: binary/octet-stream while it should be content-type: application/wasm.
Im wondering why feature requests like: https://github.com/aws/aws-cdk/issues/7090 https://github.com/aws/aws-cdk/issues/4687
Don’t have any traction, since our old s3 cp task could do this simply in a heartbeat.
Is it possible to fix this mime type, or for consumers to alter headers per file type OR patterns in a simple way without first including part x then excluding part y then including part y excluding part z. It’s not readable and not maintainable.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The root cause is that Python’s mimetypes library (that the AWS CLI relies on to guess the MIME type) doesn’t have a mapping for WebAssembly. You can try to send a pull request to them with a new entry:
⚠️COMMENT VISIBILITY WARNING⚠️
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.