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

Types and safe disclosure

05

Define a reusable type with documentation without exposing private internals.

Related RFCs and changes

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

DIAGRAM§ 4 ↗
RFC 9457 · § 4EXAMPLE
3 / 3
Types and safe disclosureDefine a reusable type with documentation without exposing private internals.Types and safe disclosuretype URI + title + expected statusHuman-readable documentationCommon type registryinternal stack / secret: [redacted]
03
Remove internal secrets

Expose corrective information without stack traces or sensitive internals.

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

A new type specifies its URI, short title, and expected HTTP status.

  • A new type specifies its URI, short title, and expected HTTP status.
  • about:blank means no semantics beyond the HTTP status.
  • Security notes warn against disclosing implementation internals or sensitive information.
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 ↗