Join GitHub today
MDN mime type analysis #244
The unique list of mime types in SCL3 httpd config are as follows:
Django allowed_types are listed here
Two places where this might need to be migrated:
When Whitenoise serves a file (from static), it uses a built-in list to determine MIME types. There's also a WHITENOISE_MIMETYPES setting, but it's unclear to me if this replaces the list or augments it without reading the Whitenoise code, and we're currently not using it. It is unclear to me if the Apache list affects files served by Whitenoise. I'm 80% sure that it does not. A few headless integration tests would confirm this.
The Apache mime types definitely come into play when serving user uploads and legacy media files. Those appear to be covered in task #241, where the aliases for file serving are enumerated. I doubt that this list is well-synced with the files served by MDN. There are probably file extensions missing from this list (does that then use system mime types?), and there are probably file extensions here not used by MDN (maybe copied from Bugzilla).
modified the milestones:
MDN AWS Architecture Eval & Recommendation,
Jun 22, 2017
After extensively looking at the files we're serving vs how they are served from SCL3, I think we're in good shape.
I think a lot of the Apache rules were left over from the demo studio, or copied from some other project.
Attachments have the MIME type stored in the database, and set it as the
I looked for other files:
I couldn't find examples files for these rules, so we'll ignore them.
Script at https://gist.github.com/jwhitlock/ba528e8f6748992734bc31e251fae3e2, in case I need to do similar work again