Uwsgi: missing mimetypes for static file serving

[xrmx]

It looks like something is off with mimetypes as it looks like it is not passed down to the client.

Found this because i have a specific svg not loading served by uwsgi static router. This specific svg not working is missing "" header so (i suppose) browser detection does not recognize it as a svg.

Stock uwsgi:

[uwsgi-fileserve] checking for /home/rm/work/big.svg
[uwsgi-fileserve] file /home/rm/work/big.svg found, mimetype (null)

after adding this mimefile to uwsgi conf:

image/svg+xml   svg svgz

the mimetype is not null:

[uwsgi-fileserve] checking for /home/rm/work/big.svg
[uwsgi-fileserve] file /home/rm/work/big.svg found, mimetype image/svg+xml  svg svgz

And the browsers display it correctly

[WALL-E]

set mime types file path

uwsgi --ini uwsgi.ini --mimefile /etc/mime.types

If the file /etc/mime.types does not exist， you need install mailcap

sudo yum install mailcap
or
sudo apt-get install mime-support

[tehfink]

NB: uwsgi expects a plain text format of mimetypes, as opposed to nginx's dict-like; e.g.:
https://raw.githubusercontent.com/lucidfrontier45/docker-python-uwsgi/master/mime.types

[tobiasmcnulty]

FWIW, I found that I didn't actually need to tell uwsgi where this file is, I just needed to install install apk add mailcap (this is on Alpine Linux). After doing that, it started serving SVGs with the correct mime type.

[oz123]

FWIW, I found that I didn't actually need to tell uwsgi where this file is, I just needed to install install apk add mailcap (this is on Alpine Linux). After doing that, it started serving SVGs with the correct mime type.

I spent a good few hours try to understand why chrome and safari won't display the SVG logo I have (FF worked). And eventually that did it!

[matthieudesprez]

sudo apt-get install -y mime-support

was enough for my case.