A helper for combating incorrect content-type, aka a mime sniffing module for node.js
So you have made a http request and got back some headers and a response body, but you just don't know if that innocent
Content-Type header tells you what really goes on in its
doc-sniff, a much simpler implementation of whatwg mime sniffing algorithm. Specifically for those responses that can't be easily distinguished via file extensions or magic numbers, eg. HTML, XML documents.
npm install doc-sniff --save
var docsniff = ;var mime1 = ;console; // text/htmlvar mime2 = ;console; // application/atom+xmlvar mime3 = ;console; // application/xml
Currently this module will correct following mime:
It does not attempt to be overzealous at correcting subtypes; see example 3 above, if original mime is acceptable, it will not be replaced.
typeis the content-type header in response
bodyis the response body string
- returns the sniffed content-type as string
The whatwg spec has a much more thorough algorithm and mime list for browser vendors, but on server-side, we are more interested in parsable documents and information extractions, if you encounter a use case not covered by this algorithm, please let us know on github issues.
Like any simple algorithm, this can easily be spoofed, so don't use it for validation, use it for mime sniffing incoming documents only.