From 7e85b9d56afb78b8cfd867db30db7d6b70f007d6 Mon Sep 17 00:00:00 2001 From: "Olivier Wilkinson (reivilibre)" Date: Wed, 14 Aug 2019 11:03:55 +0100 Subject: [PATCH] Acknowledge other potential error responses for fallback Signed-off-by: Olivier Wilkinson (reivilibre) --- .../2197-search_filter_in_federation_publicrooms.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/proposals/2197-search_filter_in_federation_publicrooms.md b/proposals/2197-search_filter_in_federation_publicrooms.md index 37e3fe7d6..5d1ae7c1c 100644 --- a/proposals/2197-search_filter_in_federation_publicrooms.md +++ b/proposals/2197-search_filter_in_federation_publicrooms.md @@ -106,9 +106,14 @@ any worse than the current one, and it is expected that large homeservers would be quick to upgrade to support this feature once it is available. In addition, as the `POST` method was not previously accepted on the -`/publicRooms` endpoint over federation, then it is not a difficult task to use -an `M_UNRECOGNIZED` standard error response `errcode` as a signal that fallback -is required. +`/publicRooms` endpoint over federation, then it is possible to fall back to the +old behaviour, if one of the following errors is encountered: + +- an `M_UNRECOGNIZED` standard error response `errcode` (this is what would be + typically expected in this situation) +- an `M_NOT_FOUND` standard error response +- a `404 Not Found` HTTP error response +- a `405 Method Not Allowed` HTTP error response ## Security considerations