Visual RFC.
ALL RFCs / RFC 3986
Read the RFC ↗
RFC 3986 / ANATOMY

The five URI components

01

A URI is parsed into scheme, authority, path, query, and fragment before its meaning is interpreted.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3 ↗
RFC 3986 · § 3EXAMPLE
4 / 4
The five URI componentsOne URI separates vertically into five named components with the relevant delimiters highlighted.Punctuation separates the componentshttps:scheme//example.org:8443authority/a/bpath?q=1query#partfragmenthttps://example.org:8443/a/b?q=1#part
04
Identify a secondary resource.

Fragment interpretation depends on the representation’s media type.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

The punctuation marks component boundaries.

  • The scheme ends at the first colon.
  • An authority, when present, begins after // and ends at /, ?, #, or the end.
  • A fragment begins at # and is separated before dereferencing.
DETAILS

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
All chapters in this RFC
  1. The five URI components
  2. Escape data, preserve delimiters
  3. Resolve a relative reference
  4. Authority has its own structure
  5. Normalize only what is safe
  6. An identifier can mislead
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗