Skip to content

Commit

Permalink
Clarify which endpoint the 403 was added on
Browse files Browse the repository at this point in the history
  • Loading branch information
Johennes committed Jul 23, 2024
1 parent c3d5e7e commit 6664b2f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion proposals/4170-profile-403.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 6664b2f

Please sign in to comment.