I am writing a spring download application and have noticed some warnings in chrome. He complains that, for example, web fonts (woff extension) are sent as plain / text instead of their correct mime type.
I use the usual mechanism for static files without special configuration. The source code I found looks like it is not possible to add more mimetypes to the "stock" ResourceHandler. The Resourcehandler sends mime type recognition to the servlet container, which is the default lump for spring-boot 1.2.
Am I missing something? Does anyone know a simple way to improve resource mapping in order to serve more file types with the correct mime type?
Right now I'm going to write a filter that runs for static content, and fixes that are missing spaces after the fact. Maybe I should create a function request in springsource ...; -)
mime-types spring-boot spring-mvc embedded-tomcat-8
Patrick cornelissen
source share