Byte-order mark
04EF BB BF can encode an initial U+FEFF signature, but UTF-8 has no byte-order choice.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 6 ↗
RFC 3629 · § 6EXAMPLE
3 / 3
03
Decode remaining content
Do not interpret a signature as a byte-order switch.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
The BOM is not required to determine endianness in UTF-8.
- The BOM is not required to determine endianness in UTF-8.
- Protocols should specify whether an initial signature is allowed.
- Blindly stripping meaningful data can affect signatures or character interpretation.
Examples are illustrative. Consult the linked RFC and its errata for implementation details.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy