aws s3 sync doesn't guess MIME type for .woff file

[Janpot]

I'm syncing an assets folder to S3 to be served over CDN. I noticed that .woff files get Content-Type: binary/octet-stream instead of application/font-woff.

[bnbon]

+1 for this.

[azoff]

+1

[j]

+1 (and for other font types)

[azoff]

For now I'm using this: https://github.com/dailymuse/s3-content-type-fixer

[wilsonwc]

This looks like it's actually a limitation of the Python mimetype library, maybe the code needs to be augmented to support mime types that aren't defined in that library?

[jamesls]

Yes, and internally I believe it will look at /etc/mime.types and a few other locations to get these mappings, so a temporary workaround would be for people to update that file if possible.

Otherwise I think there's two options here:

1. We can either start an additional list within the AWS CLI code based that has additional extensions->mimetype mappings.
2. We can look for and load an optional mime.types file. Say if you were to create an ~/.aws/cli/mime.types file, we would load that file and use that in addition to /etc/mime.types.

Any preferences for either approach?

[wilsonwc]

Thanks for the reply. It looks like Apache maintains an updated list that would be the same format as the /etc/mime.types. This might be appropriate to link to or include to satisfy the first option, and then still give users the ability to add/override types in a ~/.aws/cli/mime.types file as a new feature.

http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/conf/mime.types?view=markup

[wilsonwc]

I can also confirm that replacing my /etc/mime.types with the file linked above fixed the issue for me as a temporary workaround. (Using CentOS 6)

[dbinetti]

@jamesls @wilsonwc Are there any plans to to add support for the ~/.aws/cli/mime.types approach? This would be most welcome.

[ASayre]

Good Morning!

We're closing this issue here on GitHub, as part of our migration to UserVoice for feature requests involving the AWS CLI.

This will let us get the most important features to you, by making it easier to search for and show support for the features you care the most about, without diluting the conversation with bug reports.

As a quick UserVoice primer (if not already familiar): after an idea is posted, people can vote on the ideas, and the product team will be responding directly to the most popular suggestions.

We’ve imported existing feature requests from GitHub - Search for this issue there!

And don't worry, this issue will still exist on GitHub for posterity's sake. As it’s a text-only import of the original post into UserVoice, we’ll still be keeping in mind the comments and discussion that already exist here on the GitHub issue.

GitHub will remain the channel for reporting bugs.

Once again, this issue can now be found by searching for the title on: https://aws.uservoice.com/forums/598381-aws-command-line-interface

-The AWS SDKs & Tools Team