POST Inconsistency

[jaydson]

The JSONAPI spec says:

Any requests that contain content MUST include a Content-Type header whose value is application/vnd.api+json

Harvester is failing when the supposed header is sent:

curl -XPOST -H "Content-type: application/vnd.api+json" -d '{
  "artists": [ { "name": "Sepultura" }]
}' 'http://localhost:1337/artists'

The result:

{
  "errors": [
    {
      "status": 500,
      "detail": "TypeError: Cannot read property 'forEach' of undefined",
      "href": "about:blank",
      "title": "Oops, something went wrong."
    }
  ]
}

Changing the Content-type to application/json works just fine.
The inconsistency here is Harvester (or Fortune) are not following the spec IMHO.

[dclucas]

Sounds about right. And the error message could be better. Will check on the content type first, since throwing on the wrong content-type could break some extension cases...

[jaydson]

Yep.
Funny thing is when you try to set a random header, the message is pretty clear, and more than that, says that i must to use application/vnd.api+json or application/json:

curl -XPOST -H "Content-type: application/xxx" -d '{
  "artists": [ { "name": "Sepultura" }]
}' 'http://localhost:1337/artists'

Result:

{
  "errors": [
    {
      "status": 412,
      "href": "about:blank",
      "title": "Request header \"Content-Type\" must be one of: application/vnd.api+json, application/json",
      "detail": ""
    }
  ]
}