RFC 7807, "Problem Details for HTTP APIs", March 2016

Note: This RFC has been obsoleted by RFC 9457

Errata ID: 5515
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Steven
Date Reported: 2018-10-05

Section 3.1 says:

   o  "type" (string) - A URI reference [RFC3986] that identifies the
      problem type.  This specification encourages that, when
      dereferenced, it provide human-readable documentation for the
      problem type (e.g., using HTML [W3C.REC-html5-20141028]).  When
      this member is not present, its value is assumed to be
      "about:blank".

It should say:

   o  "type" (string) - A URI reference [RFC3986] that identifies the
      problem type.  This specification encourages that, when
      dereferenced, it provide human-readable documentation for the
      problem type (e.g., using HTML [W3C.REC-html5-20141028]).  When
      this member is missing or null, its value is assumed to be
      "about:blank".

Notes:

JSON objects with a null "type" are syntactically correct, but there is no information on how it should be handled.

{
"type": null,
"status": 404,
"title": "Not Found"
}

It makes sense to treat null as an alias of "about:blank" and that's how I think it should be documented.

Report New Errata