Allow 200s also for non-existing rooms

Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>
This commit is contained in:
Johannes Marbach 2026-02-26 11:53:32 +01:00
parent 0eb091576d
commit fd9989820a

View file

@ -105,9 +105,9 @@ paths:
the appropriate people. The caller must be joined to the room to report the appropriate people. The caller must be joined to the room to report
it. it.
Clients could infer whether a reported event exists based on the 404 response. Clients could infer whether a reported event or room exists based on the 404
Homeservers that wish to conceal this information MAY return 200 responses response. Homeservers that wish to conceal this information MAY return 200
regardless of the existence of the reported event. responses regardless of the existence of the reported event or room.
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 exists by timing the response. This is because only a report for an event exists by timing the response. This is because only a report for an
@ -150,8 +150,8 @@ paths:
This endpoint now requires the user to be joined to the room. This endpoint now requires the user to be joined to the room.
1.18: | 1.18: |
The `score` request parameter was removed. Additionally, servers The `score` request parameter was removed. Additionally, servers
may prevent event ID enumeration by using the 200 response may prevent event/room ID enumeration by using the 200 response
regardless of the existence of the reported event. regardless of the existence of the reported event/room.
responses: responses:
"200": "200":
description: The event has been reported successfully. description: The event has been reported successfully.