Normalize only what is safe
05Different strings can identify the same resource, but generic normalization has limits.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 6.2 ↗
RFC 3986 · § 6.2EXAMPLE
4 / 4
04
Remove HTTP’s default port.
The resulting example is http://example.org/~Ada.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Do not lowercase an entire URI.
- Scheme and host are case-insensitive; other components are generally case-sensitive unless the scheme says otherwise.
- Hexadecimal digits in percent encodings can be uppercased, and encoded unreserved characters can be decoded.
- Removing a default port is scheme-based normalization, not a universal port rule.
The examples simplify the wire representation. Follow the linked specification and application profile for implementation.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy