In information technology, header is supplemental data placed at the beginning of a block of data being stored or transmitted. In data transmission, the data following the header is sometimes called the payload or body.
It is vital that header composition follows a clear and unambiguous specification or format, to allow for parsing.
Examples
edit- E-mail header: The text (body) is preceded by header lines indicating sender, recipient, subject, sending time stamp, receiving time stamps of all intermediate and the final mail transfer agents, and much more.[1][2]
- Similar headers are used in Usenet (NNTP) messages, and HTTP headers.
- In a data packet sent via the Internet, the data (payload) are preceded by header information such as the sender's and the recipient's IP addresses, the protocol governing the format of the payload and several other formats. The header's format is specified in the Internet Protocol, see IP header.
- In data packets sent by wireless communication, and in sectors of data stored on magnetic media, typically the header begins with a syncword to allow the receiver to adapt to analog amplitude and speed variations and for frame synchronization.
- In graphics file formats, the header might give information about an image's size, resolution, number of colors, and the like.
- In archive file formats, the file header might serve as a fingerprint or signature to identify the specific file format and corresponding software utility.
- In some programming languages (for example C and C++) the functions are declared in header files.
See also
edit- Footer
- Protocol overhead
- Trailer (computing), used in computer networking
- Field (computer science)
References
edit- ^ P. Resnick, ed. (October 2008). Internet Message Format. IETF Network Working Group. doi:10.17487/RFC5322. RFC 5322. Draft Standard. Obsoletes RFC 2822. Updates RFC 4021. Updated by RFC 6854.
- ^ B. Leiba (March 2013). Update to Internet Message Format to Allow Group Syntax in the "From:" and "Sender:" Header Fields. Internet Engineering Task Force. doi:10.17487/RFC6854. ISSN 2070-1721. RFC 6854. Proposed Standard. Updates RFC 5322.