From fd9989820a7f19dadf5d433ce7c9c9432009f543 Mon Sep 17 00:00:00 2001 From: Johannes Marbach Date: Thu, 26 Feb 2026 11:53:32 +0100 Subject: [PATCH] Allow 200s also for non-existing rooms Signed-off-by: Johannes Marbach --- data/api/client-server/report_content.yaml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/data/api/client-server/report_content.yaml b/data/api/client-server/report_content.yaml index 23a8e5be..fd59c7d1 100644 --- a/data/api/client-server/report_content.yaml +++ b/data/api/client-server/report_content.yaml @@ -105,9 +105,9 @@ paths: the appropriate people. The caller must be joined to the room to report it. - Clients could infer whether a reported event exists based on the 404 response. - Homeservers that wish to conceal this information MAY return 200 responses - regardless of the existence of the reported event. + Clients could infer whether a reported event or room exists based on the 404 + response. Homeservers that wish to conceal this information MAY return 200 + responses regardless of the existence of the reported event or room. 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 @@ -150,8 +150,8 @@ paths: This endpoint now requires the user to be joined to the room. 1.18: | The `score` request parameter was removed. Additionally, servers - may prevent event ID enumeration by using the 200 response - regardless of the existence of the reported event. + may prevent event/room ID enumeration by using the 200 response + regardless of the existence of the reported event/room. responses: "200": description: The event has been reported successfully.