Connected: An Internet Encyclopedia
RFC 822 - 3.1.2. STRUCTURE OF HEADER FIELDS

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 822
Up: 3. LEXICAL ANALYSIS OF MESSAGES
Up: 3.1. GENERAL DESCRIPTION
Prev: 3.1.1. LONG HEADER FIELDS
Next: 3.1.3. UNSTRUCTURED FIELD BODIES

### 3.1.2. STRUCTURE OF HEADER FIELDS

Once a field has been unfolded, it may be viewed as being composed of a field-name followed by a colon (":"), followed by a field-body, and terminated by a carriage-return/line-feed. The field-name must be composed of printable ASCII characters (i.e., characters that have values between 33. and 126., decimal, except colon). The field-body may be composed of any ASCII characters, except CR or LF. (While CR and/or LF may be present in the actual text, they are removed by the action of unfolding the field.)

Certain field-bodies of headers may be interpreted according to an internal syntax that some systems may wish to parse. These fields are called "structured fields". Examples include fields containing dates and addresses. Other fields, such as "Subject" and "Comments", are regarded simply as strings of text.

Note: Any field which has a field-body that is defined as other than simply <text> is to be treated as a structured field.

Field-names, unstructured field bodies and structured field bodies each are scanned by their own, independent "lexical" analyzers.

Next: 3.1.3. UNSTRUCTURED FIELD BODIES

Connected: An Internet Encyclopedia
RFC 822 - 3.1.2. STRUCTURE OF HEADER FIELDS