Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-28 14:04:10 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Apply suggestions from code review

Browse source
This commit is contained in:
Richard van der Hoff 2022-07-28 13:24:57 +01:00 committed by GitHub
parent 15726ed62e
commit 2320b91a5f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 7 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/client-server-api/_index.md
View file

@ -32,7 +32,7 @@ Similarly, all endpoints require the server to return a JSON object,
with the exception of 200 responses to with the exception of 200 responses to
[`GET /_matrix/media/v3/download/{serverName}/{mediaId}`](#get_matrixmediav3downloadservernamemediaid) [`GET /_matrix/media/v3/download/{serverName}/{mediaId}`](#get_matrixmediav3downloadservernamemediaid)
and [`GET /_matrix/media/v3/thumbnail/{serverName}/{mediaId}`](#get_matrixmediav3thumbnailservernamemediaid). and [`GET /_matrix/media/v3/thumbnail/{serverName}/{mediaId}`](#get_matrixmediav3thumbnailservernamemediaid).
Servers should include a `Content-Type` header of `application/json` for all JSON responses. Servers msut include a `Content-Type` header of `application/json` for all JSON responses.
All JSON data, in requests or responses, must be encoded using UTF-8. All JSON data, in requests or responses, must be encoded using UTF-8.

5
content/identity-service-api.md
View file

@ -43,10 +43,11 @@ communication.
All `POST` and `PUT` endpoints, with the exception (for historical reasons) of [`POST All `POST` and `PUT` endpoints, with the exception (for historical reasons) of [`POST
/_matrix/identity/v2/account/logout`](#post_matrixidentityv2accountlogout), /_matrix/identity/v2/account/logout`](#post_matrixidentityv2accountlogout),
require the client to supply a request body containing a (potentially empty) require the client to supply a request body containing a (potentially empty)
JSON object. Clients are *not* required to supply a `Content-Type` header. JSON object. Clients should supply a `Content-Type` header of `application/json`
for all requests with JSON bodies, but this is not required.
Similarly, all endpoints require the server to return a JSON object. Servers Similarly, all endpoints require the server to return a JSON object. Servers
should include a `Content-Type` header of `application/json` for all JSON must include a `Content-Type` header of `application/json` for all JSON
responses. responses.
All JSON data, in requests or responses, must be encoded using UTF-8. All JSON data, in requests or responses, must be encoded using UTF-8.

5
content/server-server-api.md
View file

@ -53,10 +53,11 @@ specified in future as optional extensions.
All `POST` and `PUT` endpoints require the requesting server to supply a All `POST` and `PUT` endpoints require the requesting server to supply a
request body containing a (potentially empty) JSON object. Requesting servers request body containing a (potentially empty) JSON object. Requesting servers
are *not* required to supply a `Content-Type` header. should supply a `Content-Type` header of `application/json` for all requests
with JSON bodies, but this is not required.
Similarly, all endpoints in this specification require the destination server Similarly, all endpoints in this specification require the destination server
to return a JSON object. Servers should include a `Content-Type` header of to return a JSON object. Servers must include a `Content-Type` header of
`application/json` for all JSON responses. `application/json` for all JSON responses.
All JSON data, in requests or responses, must be encoded using UTF-8. All JSON data, in requests or responses, must be encoded using UTF-8.