Acknowledge other potential error responses for fallback
Signed-off-by: Olivier Wilkinson (reivilibre) <olivier@librepush.net>
This commit is contained in:
parent
97f856d706
commit
7e85b9d56a
1 changed files with 8 additions and 3 deletions
|
@ -106,9 +106,14 @@ any worse than the current one, and it is expected that large homeservers
|
||||||
would be quick to upgrade to support this feature once it is available.
|
would be quick to upgrade to support this feature once it is available.
|
||||||
|
|
||||||
In addition, as the `POST` method was not previously accepted on the
|
In addition, as the `POST` method was not previously accepted on the
|
||||||
`/publicRooms` endpoint over federation, then it is not a difficult task to use
|
`/publicRooms` endpoint over federation, then it is possible to fall back to the
|
||||||
an `M_UNRECOGNIZED` standard error response `errcode` as a signal that fallback
|
old behaviour, if one of the following errors is encountered:
|
||||||
is required.
|
|
||||||
|
- an `M_UNRECOGNIZED` standard error response `errcode` (this is what would be
|
||||||
|
typically expected in this situation)
|
||||||
|
- an `M_NOT_FOUND` standard error response
|
||||||
|
- a `404 Not Found` HTTP error response
|
||||||
|
- a `405 Method Not Allowed` HTTP error response
|
||||||
|
|
||||||
## Security considerations
|
## Security considerations
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue