archive
/
matrix-spec
mirror of https://github.com/matrix-org/matrix-spec
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
main
release/v1.12
dbkr/msc4178
release/v1.11
tulir/msc4142
release/v1.10
travis/msc2702-msc2701
rav/ref_objects_in_params
dkasak/foldable-sidebar
travis/knock-join
release/v1.9
release/v1.8
anoa/update_docsy
anoa/nix_flake
dbkr/3077-multi-stream-voip
release/v1.7
dbkr/2746-reliable-voip
rav/links_for_object_defs
release/v1.6
release/v1.5
release/v1.4
anoa/invite_knock_room_state
release/v1.3
push_gateway/r0.1.0
r0.0.0
0.2.0
application_service/r0.1.0
application_service/r0.1.1
application_service/r0.1.2
client-server/0.3.0
client-server/r0.1.0
client-server/r0.2.0
client-server/r0.3.0
client_server/r0.4.0
client_server/r0.5.0
client_server/r0.6.0
client_server/r0.6.1
identity_service/r0.1.0
identity_service/r0.2.0
identity_service/r0.2.1
identity_service/r0.3.0
push_gateway/r0.1.1
r0.0.1
server_server/r0.1.0
server_server/r0.1.1
server_server/r0.1.2
server_server/r0.1.3
server_server/r0.1.4
v1.1
v1.10
v1.11
v1.12
v1.2
v1.3
v1.4
v1.5
v1.6
v1.7
v1.8
v1.9
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e32d9a9af3'
${ noResults }
matrix-spec/proposals/1831-srv-after-wellknown.md

1.3 KiB
Raw Blame History

Proposal to do SRV lookups after .well-known to discover homeservers

Currently there is a logistical error proposed by MSC1708 which results in some homeservers unable to migrate to the new functionality proposed by MSC1711. This can happen if the delegated homeserver cannot obtain a valid TLS certificate for the domain, and an SRV record is used for backwards compatibility reasons.

Specifically, in order to be compatible with requests from both Synapse 0.34 and 1.0, servers can have both a SRV and a .well-known file, with Synapse presenting a certificate corresponding to the target of the .well-known. Synapse 0.34 is then happy because it will follow the SRV (and won't care about the incorrect certificate); Synapse 1.0 is happy because it will follow the .well-known (and will see the correct cert).

Proposal

We change the order of operations to perform a .well-known lookup before falling back to resolving the SRV record. This allows for domains to delegate to other hostnames and maintains backwards compatibility with older homeservers.

Tradeoffs

More HTTP hits will be made due to the .well-known lookup being first. This is somewhat mitigated by servers caching the responses appropriately, and using connection pools where possible.