From dc11176acad7c9855bb93cca3eb2b797268df2b3 Mon Sep 17 00:00:00 2001 From: Julian Reschke Date: Fri, 16 Mar 2018 15:57:29 +0100 Subject: [PATCH] bcp56bis: avoid overlong artwork line FWIW, it might also be good not to have kramdown-specific syntax here... --- draft-ietf-httpbis-bcp56bis.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/draft-ietf-httpbis-bcp56bis.md b/draft-ietf-httpbis-bcp56bis.md index c23d1d9e2..2c30a9473 100644 --- a/draft-ietf-httpbis-bcp56bis.md +++ b/draft-ietf-httpbis-bcp56bis.md @@ -139,7 +139,8 @@ be implemented, supported and used. However, this can easily lead to an unintended profile of HTTP's behaviour. For example, it's common to see specifications with language like this: - A `200 OK` response means that the widget has successfully been updated. + A `200 OK` response means that the widget has successfully been + updated. This sort of specification is bad practice, because it is adding new semantics to HTTP's status codes and methods, respectively; a recipient -- whether it's an origin server, client library,