From 74e8be3fd9fbb2e978f0d0f829b528f6478cb4e2 Mon Sep 17 00:00:00 2001 From: Johannes Marbach Date: Thu, 7 Nov 2024 15:56:53 +0100 Subject: [PATCH] Clarify that pusher URLs have a fixed path (#1974) Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> --- changelogs/push_gateway/newsfragments/1974.clarification | 1 + data/api/push-gateway/push_notifier.yaml | 6 +++--- 2 files changed, 4 insertions(+), 3 deletions(-) create mode 100644 changelogs/push_gateway/newsfragments/1974.clarification diff --git a/changelogs/push_gateway/newsfragments/1974.clarification b/changelogs/push_gateway/newsfragments/1974.clarification new file mode 100644 index 00000000..46c086a9 --- /dev/null +++ b/changelogs/push_gateway/newsfragments/1974.clarification @@ -0,0 +1 @@ +The path of HTTP pusher URLs is fixed to `/_matrix/push/v1/notify`. diff --git a/data/api/push-gateway/push_notifier.yaml b/data/api/push-gateway/push_notifier.yaml index fda29da7..9f461a1c 100644 --- a/data/api/push-gateway/push_notifier.yaml +++ b/data/api/push-gateway/push_notifier.yaml @@ -35,9 +35,9 @@ paths: updating counts of unread notifications should be idempotent and therefore do not require duplicate suppression. - Notifications are sent to the URL configured when the pusher is created. - This means that the HTTP path may be different depending on the push - gateway. + Clients interested in receiving notifications via this endpoint MUST + configure its full URI when creating the associated pusher via + [`/_matrix/client/v3/pushers/set`](/client-server-api/#post_matrixclientv3pushersset). operationId: notify requestBody: content: