Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2025-12-31 04:58:37 +01:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Mention how the content repository works over federation

Browse source 
We might want to consider promoting the media repo to it's own API, and maybe consider calling it the Media Repo rather than Content Repo.

Source of information: experience.
This commit is contained in:
Travis Ralston 2018-08-07 16:58:14 -06:00
parent 35f15ba3d8
commit 0858e7bd23
1 changed files with 14 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
specification/server_server_api.rst
View file

@ -1020,6 +1020,20 @@ the following EDU::
for the user
Content Repository
------------------
Attachments to events (images, files, etc) are uploaded to a homeserver via the
Content Repository described in the `Client-Server API`_. When a server wishes
to serve content originating from a remote server, it needs to ask the remote
server for the media.
Servers should use the server described in the Matrix Content URI, which has the
format ``mxc://{ServerName}/{MediaID}``. Servers should use the download endpoint
described in the `Client-Server API`_, being sure to use the ``allow_remote``
parameter (set to ``false``).
Signing Events
--------------