Validate byte sequences
03Correct byte roles are necessary but not enough: range and shortest-form rules matter.
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§ 4 ↗
RFC 3629 · § 4EXAMPLE
3 / 3
03
Use valid encoding
Slash is represented by the single byte 2F.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Do not decode invalid sequences or surrogate values as valid characters.
- Do not decode invalid sequences or surrogate values as valid characters.
- UTF-8 does not encode values above U+10FFFF.
- Overlong sequences can create security failures when filters and decoders disagree.
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