Visual RFC.
ALL RFCs / RFC 6750
Read the RFC ↗
RFC 6750 / MECHANISMS

URLs leave extra copies

03

A query-parameter token can persist in logs and other URL-handling systems.

Related RFCs and changes

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

DIAGRAM§ 2.3 ↗
RFC 6750 · § 2.3EXAMPLE
3 / 3
URLs leave extra copiesA query-parameter token can persist in logs and other URL-handling systems. Current state: Prefer the header.URLs leave extra copies/resource?access_token=TOKENaccess logTOKEN copystored URLTOKEN copyPrefer Authorization: BearerTLS does not remove endpoint logs or stored URLs.
03
Prefer the header

Keep bearer credentials out of the request URI.

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

RFC 6750 discourages URI-query transmission except where other methods are impossible.

  • RFC 6750 discourages URI-query transmission except where other methods are impossible.
  • Modern OAuth guidance further discourages access tokens in URLs.
  • TLS does not erase copies stored at endpoints or in logs.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Possession is the credential
  2. Put it in the request header
  3. URLs leave extra copies
  4. Errors describe different failures
  5. Limit the damage of disclosure
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗