From c79d1ac350afe14d85d3d43f204815bb11e4519e Mon Sep 17 00:00:00 2001 From: Patrick Cloke Date: Wed, 21 Jul 2021 07:41:56 -0400 Subject: [PATCH] Clarify error conditions. Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> --- proposals/3083-restricted-rooms.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/3083-restricted-rooms.md b/proposals/3083-restricted-rooms.md index da21da92..44f5773a 100644 --- a/proposals/3083-restricted-rooms.md +++ b/proposals/3083-restricted-rooms.md @@ -66,8 +66,8 @@ an error response with HTTP status code of 403 and an `errcode` of `M_FORBIDDEN` It is possible for a resident homeserver (one which receives a `/make_join` / `/send_join` request) to not know if the user is in some of the allowed rooms (due to not participating in them). If the user is not in any of the allowed rooms that -are known to the homeserver it should return an error response with HTTP status code -of 400 with an `errcode` of `M_UNABLE_TO_AUTHORISE_JOIN`. The joining server should +are known to the homeserver, and the homeserver is not participating in all listed +rooms, then it should return an error response with HTTP status code of 400 with an `errcode` of `M_UNABLE_TO_AUTHORISE_JOIN`. The joining server should attempt to join via another resident homeserver. If the resident homeserver knows that the user is not in *any* of the allowed rooms it should return an error response with HTTP status code of 403 and an `errcode` of `M_FORBIDDEN`. Note that it is a