Mirrors/api-guidelines
1
0
Fork 0
mirror of https://github.com/adidas/api-guidelines.git synced 2025-10-25 15:19:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updates protocol/use-appropriate-status-codes.md

Browse Source 
Auto commit by GitBook Editor
This commit is contained in:
apidesigner
2017-06-19 08:55:59 +00:00
parent 5a31e816db
commit 67b0b5614e
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
protocol/tls.md
View File

@@ -1,4 +1,4 @@
# Transport Layer Security (TLS) # 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. 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.

4
protocol/use-appropriate-status-codes.md
View File

@@ -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). 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: A request:
``` ```