From 4e14b5ba8ca56ab2ddbf465b9f18ceeca86a46e7 Mon Sep 17 00:00:00 2001 From: tezlm Date: Fri, 23 Sep 2022 17:51:39 -0700 Subject: [PATCH] Fix wording --- proposals/3896-appservice-media.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/proposals/3896-appservice-media.md b/proposals/3896-appservice-media.md index b4b8ce17..e7643498 100644 --- a/proposals/3896-appservice-media.md +++ b/proposals/3896-appservice-media.md @@ -6,7 +6,12 @@ can cause a lot of storage usage. This MSC proposes a way for appservices to reg ## Proposal -This proposal adds a new key to the namespaces block of appservice registration. For example: +This proposal adds a new key (`media`) to the namespaces block of appservice registration. + +Whenever the homeserver gets a request that matches the regex, it should make a http GET request +to `/_matrix/app/v1/media/{mediaId}`. + +For example: ```yaml namespaces: @@ -15,11 +20,8 @@ namespaces: regex: "foobar-.*" ``` -Whenever the homeserver gets a request that matches the regex, it should make a http GET request -to `/_matrix/app/v1/media/{mediaId}`. - -Example: using the example registration, fetching `mxc://server.tld/foobar-bazqux` should lead to a -request to `/_matrix/app/v1/media/foobar-bazqux`. +In this case, fetching `mxc://server.tld/foobar-bazqux` leads to a request to +`/_matrix/app/v1/media/foobar-bazqux`. Appservices may set `Cache-Control` on their response. Homeservers should cache the response, though they may remove cached remote media to save space.