Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shouldn't we be more strict about Content-type #36

Closed
dclucas opened this issue Dec 21, 2015 · 1 comment
Closed

Shouldn't we be more strict about Content-type #36

dclucas opened this issue Dec 21, 2015 · 1 comment
Labels

Comments

@dclucas
Copy link
Contributor

dclucas commented Dec 21, 2015

Really just a question. While the JSONAPI specs do not explicitly prohibit the use of any other content-type, the wording seems to indicate that just 'application/vnd.api+json' should be supported:

Clients MUST send all JSON API data in request documents with the header Content-Type: application/vnd.api+json without any media type parameters.

@kristofsajdak
Copy link
Contributor

yeah, seen this. I think that they mean that clients which pretend to be jsonapi 1.0 compliant must always send this. However as you say there is nothing that prohibits a server from accepting a plain old application/json content type as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants