Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify that pusher URLs have a fixed path #1974

Merged
merged 3 commits into from
Nov 7, 2024
Merged

Clarify that pusher URLs have a fixed path #1974

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c93d84c
Clarify that pusher URLs have a fixed path
Johennes Oct 14, 2024
bc5531f
Add changelog
Johennes Oct 14, 2024
5d20224
concrete -> full
anoadragon453 Nov 7, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelogs/push_gateway/newsfragments/1974.clarification
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
The path of HTTP pusher URLs is fixed to `/_matrix/push/v1/notify`.
6 changes: 3 additions & 3 deletions data/api/push-gateway/push_notifier.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down