Currently mandatory use of "Content-Type": "application/json" header

[HeberLZ]

In the past, this module used to parse json data no matter the Content-Type header was set or not, but since the inclusion of the type-is module, it has changed and now even if the data sent from the client is in json format, it won't parse it unless the Content-Type header is set to application/json.

Is this the way to use this module from now on or is this something intended to be changed in the future?

Cheers!

[Fishrock123]

If you want it to parse json, you must properly send it json. Likewise with urlencoded.
[see index.js]

[dougwilson]

Is this the way to use this module from now on or is this something intended to be changed in the future?

It is the way to use this module from now on, yes.

What content-type are you sending your JSON as, if I may ask?

[HeberLZ]

I was not setting up the Content-Type header at all, but now i am doing it the correct way. The issue ocurred during the migration of an express project from 3.x to 4.0.

Thanks for the quick response!

[dougwilson]

No problem.

[diosney]

Hi, just stumbled upon this issue.

This new behavior to only parse if the Content-type === 'application/json' is very undesired and counterproducent, since one can send a properly formatted JSON with a different and valid JSON-like content type, like application/vnd.api+json, as in my case (I'm sure there are many other use cases for this).

Any chances that in the very near future automatic detection/parsing (or even providing a custom Content-type to bodyParser options) will be added to json-like bodies/content-types?

Thanks

[dougwilson]

@diosney can you file this feature request as a new issue instead of re-using an issue that is different from what you are asking?

[diosney]

Done! #15.