Visual RFC.
ALL RFCs / RFC 9457
Read the RFC ↗
RFC 9457 / MECHANISM GUIDE

Problem type identity

02

The type URI identifies the kind of problem, while instance identifies an occurrence.

Related RFCs and changes

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

RFC 9457 · § 3.1.1EXAMPLE
3 / 3
Problem type identityThe type URI identifies the kind of problem, while instance identifies an occurrence.Problem type identitytype: https://api.example/creditinstance: /errors/42instance: /errors/43One problem class, many occurrences
03
Keep identifiers distinct

Many occurrences may share one type.

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

Consumers use the resolved type URI as the primary problem identifier.

  • Consumers use the resolved type URI as the primary problem identifier.
  • Missing type defaults to about:blank.
  • Consumers should not automatically dereference type URIs except developer-facing contexts described by the RFC.
DETAILS

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
All chapters in this RFC
  1. A problem response
  2. Problem type identity
  3. Human-readable details
  4. Extension members
  5. Types and safe disclosure
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗