From 10deff02e78362af0ebdc14c0c8ac2a1161b9b88 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?K=C3=A9vin=20Commaille?= Date: Thu, 4 May 2023 12:10:57 +0200 Subject: [PATCH] Fix internal link to asynchronous upload enpoint MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Kévin Commaille --- content/client-server-api/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index 55f9987b..cf00870b 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -24,7 +24,7 @@ Authentication](#client-authentication) for details). All `POST` and `PUT` endpoints, with the exception of [`POST /_matrix/media/v3/upload`](#post_matrixmediav3upload) and [`PUT -/_matrix/media/v3/upload/{serverName}/{mediaId}`](http://localhost:1313/client-server-api/#put_matrixmediav3uploadservernamemediaid), +/_matrix/media/v3/upload/{serverName}/{mediaId}`](#put_matrixmediav3uploadservernamemediaid), require the client to supply a request body containing a (potentially empty) JSON object. Clients should supply a `Content-Type` header of `application/json` for all requests with JSON bodies, but this is not required.