From f8a91dfd22ac48e632292126f3ff1da47386e511 Mon Sep 17 00:00:00 2001 From: Patrick Cloke Date: Tue, 22 Nov 2022 10:48:59 -0500 Subject: [PATCH] Use a before error codes. --- content/application-service-api.md | 2 +- content/client-server-api/_index.md | 2 +- content/identity-service-api.md | 4 ++-- content/push-gateway-api.md | 2 +- content/server-server-api.md | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/application-service-api.md b/content/application-service-api.md index 4ddcba90..fa24d6fd 100644 --- a/content/application-service-api.md +++ b/content/application-service-api.md @@ -167,7 +167,7 @@ because the application service may have been updated. #### Unknown routes If a request for an unsupported (or unknown) endpoint is received then the server -must respond with 404 `M_UNRECOGNIZED` error. +must respond with a 404 `M_UNRECOGNIZED` error. Similarly, a 405 `M_UNRECOGNIZED` error is used to denote an unsupported method to a known endpoint. diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index 65c3bbb1..8c2c0322 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -109,7 +109,7 @@ then try again. `M_UNRECOGNIZED` The server did not understand the request. This is expected to be returned with -an 404 HTTP status code if the endpoint is not implemented or an 405 HTTP status +a 404 HTTP status code if the endpoint is not implemented or a 405 HTTP status code if the endpoint is implemented, but the incorrect HTTP method is used. `M_UNKNOWN` diff --git a/content/identity-service-api.md b/content/identity-service-api.md index 31df0cbe..a9676120 100644 --- a/content/identity-service-api.md +++ b/content/identity-service-api.md @@ -109,8 +109,8 @@ The request contained an unrecognised value, such as an unknown token or medium. This is also used as the response if a server did not understand the request. -This is expected to be returned with an 404 HTTP status code if the endpoint is -not implemented or an 405 HTTP status code if the endpoint is implemented, but +This is expected to be returned with a 404 HTTP status code if the endpoint is +not implemented or a 405 HTTP status code if the endpoint is implemented, but the incorrect HTTP method is used. `M_THREEPID_IN_USE` diff --git a/content/push-gateway-api.md b/content/push-gateway-api.md index 363b45be..5fb36d7c 100644 --- a/content/push-gateway-api.md +++ b/content/push-gateway-api.md @@ -42,7 +42,7 @@ notification provider (e.g. APNS, GCM). ### Unsupported endpoints If a request for an unsupported (or unknown) endpoint is received then the server -must respond with 404 `M_UNRECOGNIZED` error. +must respond with a 404 `M_UNRECOGNIZED` error. Similarly, a 405 `M_UNRECOGNIZED` error is used to denote an unsupported method to a known endpoint. diff --git a/content/server-server-api.md b/content/server-server-api.md index d06d1709..1f325e27 100644 --- a/content/server-server-api.md +++ b/content/server-server-api.md @@ -87,7 +87,7 @@ Transparency](https://www.certificate-transparency.org/) project. ### Unsupported endpoints If a request for an unsupported (or unknown) endpoint is received then the server -must respond with 404 `M_UNRECOGNIZED` error. +must respond with a 404 `M_UNRECOGNIZED` error. Similarly, a 405 `M_UNRECOGNIZED` error is used to denote an unsupported method to a known endpoint.