From 67b0b5614ed9c213ed2645a5e841d74ac326a649 Mon Sep 17 00:00:00 2001 From: apidesigner Date: Mon, 19 Jun 2017 08:55:59 +0000 Subject: [PATCH] Updates protocol/use-appropriate-status-codes.md Auto commit by GitBook Editor --- protocol/tls.md | 2 +- protocol/use-appropriate-status-codes.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/protocol/tls.md b/protocol/tls.md index 46c79cc..1dad60a 100644 --- a/protocol/tls.md +++ b/protocol/tls.md @@ -1,4 +1,4 @@ # Transport Layer Security (TLS) -Every API **MUST** require secure connections with TLS 1.2. That is, an API using the HTTP protocol **MUST** use **HTTPS**. +Every API **MUST** require secure connections with **TLS 1.2**. That is, an API using the HTTP protocol **MUST** use **HTTPS**. Any non-TLS requests **SHOULD** be ignored. In **HTTP** environments where this is not possible, a non-TLS request **SHOULD** result in the **403 Forbidden** response. \ No newline at end of file diff --git a/protocol/use-appropriate-status-codes.md b/protocol/use-appropriate-status-codes.md index c66d6f4..e2489da 100644 --- a/protocol/use-appropriate-status-codes.md +++ b/protocol/use-appropriate-status-codes.md @@ -5,9 +5,9 @@ Every API designer, implementer and consumer **MUST** understand the semantic of At a minimum everyone **MUST** be familiar with the semantics of ["Common" HTTP Status Codes](https://github.com/for-GET/know-your-http-well/blob/master/status-codes.md#common). ---- +#### Example -#### Example: Use Codes 4xx or 5xx to Communicate Errors +#### Use Codes 4xx or 5xx to Communicate Errors A request: ```