Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-05 19:24:10 +01:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Move option to consistently respond with 200 to user reporting endpoint

Browse source
This commit is contained in:
Johannes Marbach 2025-03-21 10:04:50 +01:00
parent ebc71218d2
commit 97bf30b7a3
2 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
content/client-server-api/modules/report_content.md
View file

@ -36,11 +36,6 @@ reported user is joined to. This is because users can be exposed to harmful
content without being joined to a room. For instance, through user content without being joined to a room. For instance, through user
directories or invites. directories or invites.
Clients can infer whether a reported event, room or user exists based on the
404 responses of the reporting endpoints. Homeservers that wish to conceal
this information MAY return 200 responses regardless of the existence of the
reported subject.
Furthermore, it might be possible for clients to deduce whether a reported Furthermore, it might be possible for clients to deduce whether a reported
event, room or user exists by timing the response. This is because only a event, room or user exists by timing the response. This is because only a
report for an existing subject will require the homeserver to do further report for an existing subject will require the homeserver to do further

8
data/api/client-server/report_content.yaml
View file

@ -169,6 +169,10 @@ paths:
that the reported user is joined to. that the reported user is joined to.
Clients may wish to [ignore](#ignoring-users) users after reporting them. Clients may wish to [ignore](#ignoring-users) users after reporting them.
Clients could infer whether a reported user exists based on the 404 response.
Homeservers that wish to conceal this information MAY return 200 responses
regardless of the existence of the reported user.
operationId: reportUser operationId: reportUser
parameters: parameters:
- in: path - in: path
@ -198,7 +202,9 @@ paths:
- accessTokenBearer: [] - accessTokenBearer: []
responses: responses:
"200": "200":
description: The user has been reported successfully. description: |
The user has been reported successfully or the server chose
to not disclose whether the users exists.
content: content:
application/json: application/json:
schema: schema: