From 6664b2fbf601515946a9b3a5a075217dbc124f8e Mon Sep 17 00:00:00 2001 From: Johannes Marbach Date: Tue, 23 Jul 2024 11:42:42 +0200 Subject: [PATCH] Clarify which endpoint the 403 was added on --- proposals/4170-profile-403.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/4170-profile-403.md b/proposals/4170-profile-403.md index 8586b5ffe7d..f4e9792d916 100644 --- a/proposals/4170-profile-403.md +++ b/proposals/4170-profile-403.md @@ -42,7 +42,7 @@ this behaviour didn't end up being documented at all for the profile endpoints. Later, Synapse implemented[^2] a switchable feature to disable profile look-up over federation via a 403 `M_FORBIDDEN` response. [MSC3550] picked up on this feature and introduced this response type in the spec though only on the -client-server API. +`GET /_matrix/client/v3/profile/{userId}` endpoint in the client-server API. The current proposal aims to restore consistency among the profile endpoints by standardizing their 403 error response format and behaviour.