mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-07-02 12:17:47 +02:00
Merge f33aaa1be4 into 68ffc62de3
This commit is contained in:
commit
e661ec9202
1
changelogs/client_server/newsfragments/2404.breaking
Normal file
1
changelogs/client_server/newsfragments/2404.breaking
Normal file
|
|
@ -0,0 +1 @@
|
|||
Clients are now supposed to follow 30x redirects from `/.well-known/matrix/client` as per [MSC4402](https://github.com/matrix-org/matrix-spec-proposals/pull/4402).
|
||||
|
|
@ -429,6 +429,7 @@ Instead, they can be reached via HTTPS on the [server name](/appendices/#server-
|
|||
|
||||
Servers hosting the `.well-known` JSON file SHOULD offer CORS headers,
|
||||
as per the [CORS](#web-browser-clients) section in this specification.
|
||||
{{% added-in v="1.19" %}} Servers SHOULD also ensure that each 30x redirect, if any, offers such CORS headers.
|
||||
{{% /boxes/note %}}
|
||||
|
||||
The flow for auto-discovery is as follows:
|
||||
|
|
@ -437,6 +438,7 @@ The flow for auto-discovery is as follows:
|
|||
Matrix ID at the first colon.
|
||||
2. Extract the hostname from the server name as described by the [grammar](/appendices/#server-name).
|
||||
3. Make a GET request to `https://hostname/.well-known/matrix/client`.
|
||||
{{% added-in v="1.19" %}} 30x redirects SHOULD be followed, however redirection loops should be avoided.
|
||||
1. If the returned status code is 404, then `IGNORE`.
|
||||
2. If the returned status code is not 200, or the response body is
|
||||
empty, then `FAIL_PROMPT`.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,5 @@
|
|||
# Copyright 2018 New Vector Ltd
|
||||
# Copyright 2026 Hagen Echzell
|
||||
#
|
||||
# Licensed under the Apache License, Version 2.0 (the "License");
|
||||
# you may not use this file except in compliance with the License.
|
||||
|
|
@ -20,7 +21,11 @@ paths:
|
|||
get:
|
||||
summary: Gets Matrix server discovery information about the domain.
|
||||
description: |-
|
||||
Gets discovery information about the domain. The file may include
|
||||
Gets discovery information about the domain.
|
||||
{{% added-in v="1.19" %}} Clients SHOULD follow 30x redirects, carefully
|
||||
avoiding redirect loops, and use normal X.509 certificate validation.
|
||||
|
||||
The file may include
|
||||
additional keys, which MUST follow the Java package naming convention,
|
||||
e.g. `com.example.myapp.property`. This ensures property names are
|
||||
suitably namespaced for each application and reduces the risk of
|
||||
|
|
|
|||
Loading…
Reference in a new issue