From a1621c7ae6cf1e78736a5a93234164ce92ac07fa Mon Sep 17 00:00:00 2001 From: Lucas Pardue Date: Fri, 2 Feb 2018 22:54:17 +0000 Subject: [PATCH] bcp56bis: Status code reason phrase Port over of PR from mnot repo. Modified last sentence to avoid to much usage of the word "further". --- draft-ietf-httpbis-bcp56bis.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/draft-ietf-httpbis-bcp56bis.md b/draft-ietf-httpbis-bcp56bis.md index d79446283..03e5b6085 100644 --- a/draft-ietf-httpbis-bcp56bis.md +++ b/draft-ietf-httpbis-bcp56bis.md @@ -383,9 +383,9 @@ application is harmful, as these are not generic semantics, since the consumer n context of the application to understand them. Furthermore, applications using HTTP MUST NOT re-specify the semantics of HTTP status codes, even -if it is only by copying their definition. They MUST NOT require specific status phrases to be -used; the status phrase has no function in HTTP, and is not guaranteed to be preserved by -implementations. +if it is only by copying their definition. They MUST NOT require specific reason phrases to be +used; the reason phrase has no function in HTTP, and is not guaranteed to be preserved by +implementations. The reason phrase is not carried in the {{RFC7540}} message format. Typically, applications using HTTP will convey application-specific information in the message body and/or HTTP header fields, not the status code.