Historically, HTTP has allowed field content with text in the ISO-8859-1 charset [ISO-8859-1], supporting other charsets only through use of [RFC2047] encoding. In practice, most HTTP header field values use only a subset of the US-ASCII charset [USASCII]. Newly defined header fields SHOULD limit their field values to US-ASCII octets. A recipient SHOULD treat other octets in field content (obs-text) as opaque data.
The body of http message can be anything you like... But headers not.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
One issue is that the type of values passed through HTTP headers is always a string.
Not really. Content-Length for example is an integer.
It's still a string, a string representation of an integer, but a string none the less.
So is JSON and XML. It's one big string of characters.
The body is also a string, of a HTTP request and response.
Yes, body is a raw data that you can serialize to represent values with types (usually according to Content-Type header).
See RFC 723. tools.ietf.org/html/rfc7230#sectio...
The body of http message can be anything you like... But headers not.