The Content-Type header is used as specified in [RFC2616]. However, because this document describes messages for the application/atom+xml (section 126.96.36.199.1), application/json (section 188.8.131.52.2), application/json;odata=verbose (section 184.108.40.206.3), application/xml, text/plain, and text/xml formats, a data service client or server SHOULD only use HTTP messages with a Content-Type header value as shown in the ABNF grammar that follows and is specified in [RFC5234]. The exception to the above rule is when messages are used that represent a Media Resource [RFC5023] or the raw value of an entity's property (see section 220.127.116.11).
Content-Type = "Content-Type:" ("application/atom+xml" / "application/atom+xml;type=entry" / "application/atom+xml;type=feed" / "application/json;odata=verbose" / "application/json" / "application/xml" / "text/plain" / "text/xml" / "octet/stream") CRLF ";" <Remainder of rule is per the Content-Type rule in [RFC2616]>
Listing: Content-Type Header ABNF Grammar
Example: Content-Type: application/atom+xml;charset=UTF-8