[art] [Technical Errata Reported] RFC7807 (6178)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 18 May 2020 05:45 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27A753A0813 for <art@ietfa.amsl.com>; Sun, 17 May 2020 22:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OkaXSlxCFdzU for <art@ietfa.amsl.com>; Sun, 17 May 2020 22:45:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCFE23A0810 for <art@ietf.org>; Sun, 17 May 2020 22:45:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8E0D3F40759; Sun, 17 May 2020 22:45:22 -0700 (PDT)
To: mnot@mnot.net, erik.wilde@dret.net, superuser@gmail.com, barryleiba@computer.org, superuser@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: gary@realify.com, art@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200518054522.8E0D3F40759@rfc-editor.org>
Date: Sun, 17 May 2020 22:45:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/XjCxw-ATlH6Cj4MlGK4vNt8H8-o>
Subject: [art] [Technical Errata Reported] RFC7807 (6178)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 May 2020 05:45:27 -0000
The following errata report has been submitted for RFC7807, "Problem Details for HTTP APIs". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6178 -------------------------------------- Type: Technical Reported by: Gary Peck <gary@realify.com> Section: 3 Original Text ------------- The ability to convey problem-specific extensions allows more than one problem to be conveyed. For example: HTTP/1.1 400 Bad Request Content-Type: application/problem+json Content-Language: en { "type": "https://example.net/validation-error", "title": "Your request parameters didn't validate.", "invalid-params": [ { "name": "age", "reason": "must be a positive integer" }, { "name": "color", "reason": "must be 'green', 'red' or 'blue'"} ] } Corrected Text -------------- The ability to convey problem-specific extensions allows more than one problem to be conveyed. For example: HTTP/1.1 400 Bad Request Content-Type: application/problem+json Content-Language: en { "type": "https://example.net/validation-error", "title": "Your request parameters didn't validate.", "invalid_params": [ { "name": "age", "reason": "must be a positive integer" }, { "name": "color", "reason": "must be 'green', 'red' or 'blue'"} ] } Notes ----- The "invalid-params" member in the example is named incorrectly. According to Section 4, it should contain an "_" rather than a "-" in its name: > If such additional members are defined, their names SHOULD start with > a letter (ALPHA, as per [RFC5234], Appendix B.1) and SHOULD consist > of characters from ALPHA, DIGIT ([RFC5234], Appendix B.1), and "_" > (so that it can be serialized in formats other than JSON), and they > SHOULD be three characters or longer. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC7807 (draft-ietf-appsawg-http-problem-03) -------------------------------------- Title : Problem Details for HTTP APIs Publication Date : March 2016 Author(s) : M. Nottingham, E. Wilde Category : PROPOSED STANDARD Source : ART Area General Application Working Group Area : Applications and Real-Time Stream : IETF Verifying Party : IESG
- [art] [Technical Errata Reported] RFC7807 (6178) RFC Errata System
- Re: [art] [Technical Errata Reported] RFC7807 (61… Mark Nottingham