History

rui hildt 4f5db9ab26 Add initial version of dijkstra backend cloudron image		2020-10-12 11:27:15 +02:00
..
dist	Add initial version of dijkstra backend cloudron image	2020-10-12 11:27:15 +02:00
CHANGELOG.md	Add initial version of dijkstra backend cloudron image	2020-10-12 11:27:15 +02:00
LICENSE	Add initial version of dijkstra backend cloudron image	2020-10-12 11:27:15 +02:00
README.md	Add initial version of dijkstra backend cloudron image	2020-10-12 11:27:15 +02:00
package.json	Add initial version of dijkstra backend cloudron image	2020-10-12 11:27:15 +02:00

README.md

"Don't infer the MIME type" middleware

Some browsers will try to "sniff" mimetypes. For example, if my server serves file.txt with a text/plain content-type, some browsers can still run that file with <script src="file.txt"></script>. Many browsers will allow file.js to be run even if the content-type isn't for JavaScript.

Browsers' same-origin policies generally prevent remote resources from being loaded dangerously, but vulnerabilities in web browsers can cause this to be abused. Some browsers, like Chrome, will further isolate memory if the X-Content-Type-Options header is seen.

There are some other vulnerabilities, too.

This middleware prevents Chrome, Opera 13+, IE 8+ and Firefox 50+ from doing this sniffing. The following example sets the X-Content-Type-Options header to its only option, nosniff:

const nosniff = require('dont-sniff-mimetype')
app.use(nosniff())

MSDN has a good description of how browsers behave when this header is sent.