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

Don't explain what a 400 Bad Request is

Browse source
This commit is contained in:
Travis Ralston 2018-08-02 18:47:17 -06:00
parent 05bb7e1050
commit 0b313dbdd9
1 changed files with 1 additions and 28 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

29
api/server-server/query.yaml
View file

@ -49,8 +49,7 @@ paths:
description: |- description: |-
Performs a query to get the mapped room ID and list of resident homeservers in Performs a query to get the mapped room ID and list of resident homeservers in
the room for a given room alias. Homeservers should only query room aliases the room for a given room alias. Homeservers should only query room aliases
that belong to the target server (idenfified by the DNS Name in the alias). that belong to the target server (identified by the DNS Name in the alias).
The target server may not appear in the resident servers list.
Servers may wish to cache the response to this query to avoid requesting the Servers may wish to cache the response to this query to avoid requesting the
information too often. information too often.
@ -92,17 +91,6 @@ paths:
"another.example.com:8449", "another.example.com:8449",
] ]
} }
400:
description: |-
The room alias is not hosted on the server. This can happen if the directory
server is named "example.org" and the room alias ends with "matrix.org".
schema:
$ref: "../client-server/definitions/errors/error.yaml"
examples:
application/json: {
"errcode": "M_UNKNOWN",
"error": "Room alias not hosted on this homeserver."
}
404: 404:
description: The room alias was not found. description: The room alias was not found.
schema: schema:
@ -167,21 +155,6 @@ paths:
"displayname": "John Doe", "displayname": "John Doe",
"avatar_url": "mxc://matrix.org/MyC00lAvatar" "avatar_url": "mxc://matrix.org/MyC00lAvatar"
} }
400:
description: |-
The request was missing parameters or had invalid values for the parameters. This
can happen for:
* The user not being hosted on the homeserver,
* Lack of a ``user_id`` in the request, or
* The ``field`` requested not being an allowed value.
schema:
$ref: "../client-server/definitions/errors/error.yaml"
examples:
application/json: {
"errcode": "M_INVALID_ARGUMENT_VALUE",
"error": "User is not hosted on this homeserver."
}
404: 404:
description: The user does not exist or does not have a profile. description: The user does not exist or does not have a profile.
schema: schema: