1 chat request from
Header fields can be extended over multiple lines by preceding each extra line with at least one SP or HT.
Applications ought to follow "common form", where one is known or indicated, when generating HTTP constructs, since there might exist some implementations that fail to accept anything beyond the common forms.
The presence of a message-body in a request is signaled by the inclusion of a Content-Length or Transfer-Encoding header field in the request's message-headers.
Messages MUST NOT include both a Content-Length header field and a non-identity transfer-coding.
If the message does include a non- identity transfer-coding, the Content-Length MUST be ignored.
The message-body (if any) of an HTTP message is used to carry the entity-body associated with the request or response.
The message-body differs from the entity-body only when a transfer-coding has been applied, as indicated by the Transfer-Encoding header field (section 14.41).