Skip to content

Commit

Permalink
List regexps for account data and presence only for GET requests
Browse files Browse the repository at this point in the history
GET requests can still be handled by any generic worker, not just the
stream writer.
  • Loading branch information
evoL committed Dec 6, 2024
1 parent f10c1f4 commit 6ff1d12
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 1 deletion.
2 changes: 1 addition & 1 deletion changelog.d/17954.doc
Original file line number Diff line number Diff line change
@@ -1 +1 @@
Removed redundant regular expressions for account data, receipts and presence requests from the documentation on generic_worker. Contributed by @evoL.
Reorganized regular expressions for account data, receipts and presence requests in the documentation on generic_worker. This is because POST requests to those paths require the worker to be configured as a stream writer. Contributed by @evoL.
7 changes: 7 additions & 0 deletions docs/workers.md
Original file line number Diff line number Diff line change
Expand Up @@ -281,6 +281,13 @@ Additionally, the following REST endpoints can be handled for GET requests:
^/_matrix/client/(api/v1|r0|v3|unstable)/pushrules/
^/_matrix/client/unstable/org.matrix.msc4140/delayed_events

# Account data requests
^/_matrix/client/(r0|v3|unstable)/.*/tags
^/_matrix/client/(r0|v3|unstable)/.*/account_data

# Presence requests
^/_matrix/client/(api/v1|r0|v3|unstable)/presence/

Pagination requests can also be handled, but all requests for a given
room must be routed to the same instance. Additionally, care must be taken to
ensure that the purge history admin API is not used while pagination requests
Expand Down

0 comments on commit 6ff1d12

Please sign in to comment.