All specs
RFC 3986RFCMust KnowBack OfficeProduct2005

Uniform Resource Identifier Syntax

Naming & Addressing·RFC Editor
WHY YOU NEED THIS

Every URL in your app, API, auth redirect, webhook, or deep link is built on this grammar. Essential for routing, redirects, and OAuth callback validation.

What It Defines

Defines the generic syntax for URIs: scheme, authority, path, query, fragment. Establishes absolute vs relative references, percent-encoding, normalization, and resolution rules.

Canonical (Normative)

Convenient (Practical)

Related References

uriurlsyntaxnaming
Standards Body
RFC Editor

The canonical publication point for finalized RFCs. If a protocol is standardized as an RFC, the RFC Editor text is the normative final reference. Published by the IETF, IRTF, IAB, and independent stream.

Visit

Related Specs

WHATWG URLWHATWGMust Know

URL Standard

Browsers parse URLs per this standard, not raw RFC 3986. Critical for client-side routing, form encoding, and cross-origin behavior.

ProductNaming & Addressing
Details
RFC 9110RFCMust Know

HTTP Semantics

This is the core contract of every web API, browser request, and server response. You can't design or debug HTTP without knowing this.

ProductHTTP
Details