content
If this header is set, its value MUST be a MIME type that describes the format of the body. Otherwise, the receiver SHOULD consider the body to be a binary blob.
The implied text encoding for MIME types starting with text/ is UTF-8. If you are using a text-based MIME type with a different encoding then you SHOULD append ;charset=<encoding> to the MIME type.
For example, text/html;charset=utf-16 SHOULD be used if you're sending an HTML body in UTF-16 encoding. The ;charset=<encoding> SHOULD also get appended to any non text/ MIME types which can be interpreted as text. A good example of this would be a UTF-8 encoded XML. Its content-type SHOULD get set to application/xml;charset=utf-8.
All STOMP clients and servers MUST support UTF-8 encoding and decoding. Therefore, for maximum interoperability in a heterogeneous computing environment, it is RECOMMENDED that text-based content be encoded with UTF-8.