Hi Alex, Hi Alexis,

i added/rephrased this section in the documentation with PR #91 resolving issue #57. I believe this is still valid, since it's about "Content-Type" **header validation**, which happens **before** request **body deserializing** and is technically also completely independent from it.

Especially the constraints on the "Accept" http request header have nothing to do with the ingress request body, but rather with the egress response body.

Maybe we should rephrase the introductional sentence again, so instead of having:
> Content validation
> ==================
> There are two flavors of content validations cornice can apply to services:

this could make it more clear:
> Content-Type- and Accept-header validation
> ==================================
> There are two flavors of constraints cornice can apply to http request headers:

What do you think?

Cheers,
Andreas.