Clarify that pusher URLs have a fixed path (#1974)
Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>
This commit is contained in:
parent
909c4614ac
commit
74e8be3fd9
2 changed files with 4 additions and 3 deletions
1
changelogs/push_gateway/newsfragments/1974.clarification
Normal file
1
changelogs/push_gateway/newsfragments/1974.clarification
Normal file
|
@ -0,0 +1 @@
|
||||||
|
The path of HTTP pusher URLs is fixed to `/_matrix/push/v1/notify`.
|
|
@ -35,9 +35,9 @@ paths:
|
||||||
updating counts of unread notifications should be idempotent and
|
updating counts of unread notifications should be idempotent and
|
||||||
therefore do not require duplicate suppression.
|
therefore do not require duplicate suppression.
|
||||||
|
|
||||||
Notifications are sent to the URL configured when the pusher is created.
|
Clients interested in receiving notifications via this endpoint MUST
|
||||||
This means that the HTTP path may be different depending on the push
|
configure its full URI when creating the associated pusher via
|
||||||
gateway.
|
[`/_matrix/client/v3/pushers/set`](/client-server-api/#post_matrixclientv3pushersset).
|
||||||
operationId: notify
|
operationId: notify
|
||||||
requestBody:
|
requestBody:
|
||||||
content:
|
content:
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue